Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

xpipe.io

Post reply on HN
Print view View original

51–60 of 84 posts

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#51

Post by sepositus »

Question for the developer: for the Kubernetes integration, I use aws-vault to generate short-lived credentials to authenticate with my clusters (meaning, by default, kubectl doesn't work outside of this context).

Would it be possible to get XPipe to work with this constraint? Couldn't find much in the docs.

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#52

Post by axkdev »

Hi! Looks like a very interesting tool, as a stubborn cli-only user, I was pleased that there is cli version of this alongside the GUI verison. However, trying to look into the documentation of the cli has left me with a 404 page. https://docs.xpipe.io/cli/man

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#53

Post by crschnick »

axkdev wrote: post #52

Hi! Looks like a very interesting tool, as a stubborn cli-only user, I was pleased that there is cli version of this alongside the GUI verison. However, trying to look into the documentation of the cli has left me with a 404 page. https://docs.xpipe.io/cli/man

Whoops, it seems like some links were not updated yet. That should be just https://docs.xpipe.io/cli

To preface that, the CLI is only very basic. The only real thing you can do with it is launch shell connections. For more advanced usage without the GUI, there is for example the Python API: https://docs.xpipe.io/guide/python-api

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#54

Post by robertlagrant »

globular-toast wrote: post #44
robertlagrant wrote: post #32

Earlier quoted context omitted.

Can you name the top three reasons why Go or Rust would be better for this?

1. Rust is cool, 2. Go is cool, 3. Java is uncool.

That is pretty persuasive!

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#55

Post by crschnick »

sepositus wrote: post #51

Question for the developer: for the Kubernetes integration, I use aws-vault to generate short-lived credentials to authenticate with my clusters (meaning, by default, kubectl doesn't work outside of this context). Would it be possible to get XPipe to work with this constraint? Couldn't find much in the docs.

Now I don't fully know the details of your setup, but in general XPipe just works on top of your kubectl installation. So it will only work if you could manually connect to your clusters via kubectl in a terminal. But you can always just try it out and see what happens the community version because I can't say that for sure.

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#57

Post by crschnick »

sleepybrett wrote: post #56

i can already "access my entire infrastructre from my local desktop" using software that costs me $0 a month.

That is true, but ideally with XPipe you can do that easier and faster. And with the time and effort you save each month, the few $ per month can be good deal for you.

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#58

Post by von_lohengramm »

> Windows enterprise systems are only supported with at least a XPipe Professional license. You can find information about upgrading to a professional license below.

Welp. If I have to choose between XPipe and LTSC, I'm afraid LTSC is gonna win. I have no interest running a version of Windows where Windows Update will randomly decide to brick my install or better yet, add even more Candy Crushes to my start menu.

Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more

#59

Post by sepositus »

crschnick wrote: post #55
sepositus wrote: post #51

Question for the developer: for the Kubernetes integration, I use aws-vault to generate short-lived credentials to authenticate with my clusters (meaning, by default, kubectl doesn't work outside of this context). Would it be possible to get XPipe to work with this constraint? Couldn't find much in the docs.

Now I don't fully know the details of your setup, but in general XPipe just works on top of your kubectl installation. So it will only work if you could manually connect to your clusters via kubectl in a terminal. But you can always just try it out and see what happens the community version because I can't say that for sure.

Yeah, I'm assuming you're just calling kubectl directly underneath the hood. The way that aws-vault works is that you do something like: `aws-vault exec kubectl ...` or you can just do `aws-vault exec` and drop into a subshell. In both cases, a set of short-lived AWS credentials are exposed via the AWS-defined environment variables to the process (or shell context). The kubeconfig is then configured to handle authentication via AWS (rather than the default certificate method).

So, if you just straight-up call `kubectl` within XPipe without having AWS credentials already available, then it would fail. So, I'm guessing this wouldn't work.

Post reply on HN