Skip to content
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.

Enable setting services with NodePorts #373

Open
Fizzadar opened this issue Jan 5, 2016 · 2 comments
Open

Enable setting services with NodePorts #373

Fizzadar opened this issue Jan 5, 2016 · 2 comments

Comments

@Fizzadar
Copy link

Fizzadar commented Jan 5, 2016

Currently NodePort has to be defined within the service manifest (as normal Kube config). However it might be useful to provide a --nodeport CLI argument during install that simply adds type: NodePort to any services created (the argument could optionally take the port number).

This would avoid forcing the creation of the extra iptables rules for every service, but also enable people to provide external access to services installed with Helm.

@Fizzadar Fizzadar changed the title Enable setting services up as NodePorts Enable setting services with NodePorts Jan 5, 2016
@sputnick
Copy link

+1

gabrtv pushed a commit to gabrtv/helm that referenced this issue Jun 30, 2016
fix(version): use build version in helm
@listingmirror
Copy link

Is there a workaround for this? Or how do we use nodeports with helm? Specifically looking at redis... seems no built in way to do a nodeport. Do I need my own service I define outside of helm?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants