You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Fizzadar
changed the title
Enable setting services up as NodePorts
Enable setting services with NodePorts
Jan 5, 2016
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 addstype: 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.
The text was updated successfully, but these errors were encountered: