-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: implement service type NodePort #2986
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
eeefb5c to
2aacee5
Compare
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
2aacee5 to
268047e
Compare
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
268047e to
2552ad0
Compare
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
8a1d100 to
c6d5948
Compare
|
Cannot start a pipeline due to: Click on pipeline status check Details link below for more information. |
This PR adds support for Kubernetes services of type
NodePort.I tried my best to keep the structure of the configuration and code the same as for the LoadBalancer service type.
If the configuration for the NodePort is enabled the LoadBalancer configuration is overwritten.
Specific ports to be used on the kubernetes node(s) can be specified, if left empty kubernetes picks a port based on the clusters configuration: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
Implements #983
Probably supersedes #994
Since this is my first PR at Zalando and this repository, please feel free to let me know if you would like me to make changes, if you want a specific test or if I need to bump a version somewhere. Thank you!