i would like to suggest a ipmi-kvm integration for like dell idrac, hp ilo, supermicro bmc
Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
71–80 of 84 posts
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#72i would like to suggest a ipmi-kvm integration for like dell idrac, hp ilo, supermicro bmc
The current KVM integration is actually more formally an integration for libvirt and the virsh command-line tool.
If your hypervisor is supported by libvirt, you should already be able to use it in XPipe.
If it does not support libvirt, then I guess this would need a separate integration. But I would have to look into that first as I have never used these tools you listed.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#73Earlier quoted context omitted.
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 authent…
I'm also an aws-vault user and wanted to draw your attention to the fact that kubectl supports exec based credential acquisition (in fact, that's how $(aws eks update-kubeconfig) emits them by default). Now, whether that fits your threat model is a different story, but it's for sure technically possible because I use that setup every day
By default, it looks like this:
exec:
command: aws
args:
- --region
- us-east-2
- eks
- get-token
- --cluster-name
- my-cluster
exec:
command: aws-vault
args:
- exec
- --region
- us-east-2
- my-vault-profile
- --
- aws
# likely not required, but I'm including it for "coding in a textarea" :-)
- --region
- us-east-2
- eks
- get-token
- --cluster-name
- my-clusterRe: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#74Earlier quoted context omitted.
What os are you using? And about adversity to subscriptions, note that you can also obtain lifetime licenses further down the pricing page.
FYI: y'all are talking about an "aversion" and not an adversity.
You're right. I noticed it afterwards but the edit time had already expired.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#75Hmm looks interesting but all my servers require openpgp (yubikey with gpg agent support) so I'd have to use the homelab tier. And I'm very adverse to subscriptions. And I don't think it's available for my os, otherwise I'd try it. But it's ok, I have my own setups for this stuff.
What os are you using? And about adversity to subscriptions, note that you can also obtain lifetime licenses further down the pricing page.
I use BSD. But it's ok, I'm kinda happy with the setup I have. Obviously I'm not really an "out of the box" and "use it like it's meant to be used" kind of person, otherwise I definitely wouldn't have used BSD :)
And the marketshare on desktop is so tiny that there is really no value in supporting it, I understand that.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#76Do you support shortcuts for nested RDP connections. It’s a major pain point
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#77Can you expand with more technical explanation how are those two points implemented:
- You can bring your shell environments / init scripts / aliases with you in a noninvasive way. I.e. you don't have to modify the remote system dotfiles, when you connect through xpipe it will set up any scripts you want to have available automatically
- You can link up your password manager with your SSH client and other connection methods that require passwords
Feel free to write here or refer to any url you recommend.
Thank you, and good luck with your product!
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#78i 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.
it will not, i know how to write aliases.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#79Can you expand with more technical explanation how are those two points implemented: - You can bring your shell environments / init scripts / aliases with you in a noninvasive way. I.e. you don't have to modify the remote system dotfiles, when you connect through xpipe it will set up any scripts you want to have available automatically - You can link up your password manager with your SSH client and other connection…
- When XPipe will open a terminal connection and you have specified custom shell environments / init scripts for a certain system, it will first automatically create a temporary init script on the target system in the background, which will be run as the login script only for that terminal launch from XPipe. That way it's noninvasive and doesn't change any existing configuration on the system
- XPipe acts as an askpass program for SSH, meaning that it can listen to any password requests made from the ssh client, forward that your password manager, and reply with the password that the password manager returned. If you password manager supports the SSH-agent, XPipe can also use it to supply keys for ssh as well.
Re: Show HN: XPipe, a shell connection hub for SSH, Docker, K8s, VMs, and more
#80Do you support shortcuts for nested RDP connections. It’s a major pain point
There isn't good support for nested RDP connections, didn't even know that some people used something like this.
But there is very good support for nested shell connections and tunneling RDP over SSH. If your target system isn't reachable directly and require something like a bastion host connection first, you can still connect via RDP if you use SSH tunnels over multiple hops in XPipe.