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
Is this a bug report or feature request? (choose one):
Feature request
Kubernetes Version (output of kubectl version):
Any Helm Client and Tiller Versions (output of helm version):
Any Development or Deployment Environment?:
Both Release Tag or Master:
Master Expected Behavior:
Services should have a flag to enable/disable node ports What Actually Happened:
Only Horizon has this currently How to Reproduce the Issue (as minimally as possible):
n/a Any Additional Comments:
Node ports need to have a consistent numerical pattern across charts, default kubernetes NodePort range is from 30000-32767.
Is this a bug report or feature request? (choose one):
Feature request
Kubernetes Version (output of
kubectl version):Any
Helm Client and Tiller Versions (output of
helm version):Any
Development or Deployment Environment?:
Both
Release Tag or Master:
Master
Expected Behavior:
Services should have a flag to enable/disable node ports
What Actually Happened:
Only Horizon has this currently
How to Reproduce the Issue (as minimally as possible):
n/a
Any Additional Comments:
Node ports need to have a consistent numerical pattern across charts, default kubernetes NodePort range is from 30000-32767.