I guess one could use either Service.type=LoadBalancer (one ELB per service on port 22) or Service.type=NodePort with single ELB mapping ELB-PORT:NODE-PORT for each service.
-- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em dom., 17 de nov. de 2019 às 22:13, Just Marvin < marvin.the.cynical.ro...@gmail.com> escreveu: > Tobias, > > I _will_ have access to load balancers if needed, but at the moment, I > need to understand how it works. Assume that I do: what exactly does "proxy > to the internal sftp service" mean? I assume "sftp service" would be the > service that I set up, but which piece is the proxy? I don't see that load > balancer and proxy functions as being the same, so it seems like you are > talking about a third piece. What piece is that? > > Regards, > Marvin > > On Sun, Nov 17, 2019 at 1:30 PM Tobias Florek <opensh...@ibotty.net> > wrote: > >> Hi! >> >> I assume you don't have easy access to load balancers, because that >> would be easiest. Just proxy to the internal sftp service. >> >> If you don't I have used Nodeport service in the past. You will lose >> the nice port 22 though. If you control the node's ssh daemon, you can >> also use ProxyJumps. Be sure to lock down ssh for the users though. >> >> Cheers, >> Tobias Florek >> >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
