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
Make it possible to set nodePort in services (#931)
* Make it possible to set nodePort in services
* Fix copy-pasted comment
* Define nodeport for synchrony svc
* Fix unit tests
* Add docs
---------
Co-authored-by: Yevhen Ivantsov <[email protected]>
Copy file name to clipboardExpand all lines: docs/docs/userguide/CONFIGURATION.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ jira:
56
56
timeoutSeconds: 10800
57
57
```
58
58
59
-
The service port will be exposed on a random port from the ephemeral port range (`30000`-`32767`) on all worker nodes. You can provision a LoadBalancer with `443` or `80` (or both) listeners that will forward traffic to the node port (you can get service node port by running `kubectl describe $service -n $namespace`). Both LoadBalancer and Kubernetes service should be configured to maintain session affinity. LoadBalancer session affinity should be configured as per instructions for your Kubernetes/cloud provider. Service session affinity is configured by overriding the default Helm chart values (see the above example). Make sure you configure networking rules to allow the LoadBalancer to communicate with the Kubernetes cluster worker node on the node port.
59
+
The service port will be exposed on a random port from the ephemeral port range (`30000`-`32767`) on all worker nodes. It is possible to explicitly set NodePort in `service.nodePort` (make sure it's not reserved for any existing service in the cluster). You can provision a LoadBalancer with `443` or `80` (or both) listeners that will forward traffic to the node port (you can get service node port by running `kubectl describe $service -n $namespace`). Both LoadBalancer and Kubernetes service should be configured to maintain session affinity. LoadBalancer session affinity should be configured as per instructions for your Kubernetes/cloud provider. Service session affinity is configured by overriding the default Helm chart values (see the above example). Make sure you configure networking rules to allow the LoadBalancer to communicate with the Kubernetes cluster worker node on the node port.
60
60
61
61
!!!tip
62
62
For more information about Kubernetes service session affinity, see [Kubernetes documentation](https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity){.external}.
Copy file name to clipboardExpand all lines: src/main/charts/bamboo/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,7 @@ Kubernetes: `>=1.21.x-0`
87
87
| bamboo.service.annotations | object |`{}`| Additional annotations to apply to the Service |
88
88
| bamboo.service.contextPath | string |`nil`| The Tomcat context path that Bamboo will use. The ATL_TOMCAT_CONTEXTPATH will be set automatically. |
89
89
| bamboo.service.loadBalancerIP | string |`nil`| Use specific loadBalancerIP. Only applies to service type LoadBalancer. |
90
+
| bamboo.service.nodePort | string |`nil`| Only applicable if service.type is NodePort. NodePort for Bamboo service |
90
91
| bamboo.service.port | int |`80`| The port on which the Bamboo K8s Service will listen for http traffic |
91
92
| bamboo.service.sessionAffinity | string |`"None"`| Session affinity type. If you want to make sure that connections from a particular client are passed to the same pod each time, set sessionAffinity to ClientIP. See: https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity|
Copy file name to clipboardExpand all lines: src/main/charts/bitbucket/README.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,20 +122,23 @@ Kubernetes: `>=1.21.x-0`
122
122
| bitbucket.service.annotations | object |`{}`| Additional annotations to apply to the Service |
123
123
| bitbucket.service.contextPath | string |`nil`| The context path that Bitbucket will use. |
124
124
| bitbucket.service.loadBalancerIP | string |`nil`| Use specific loadBalancerIP. Only applies to service type LoadBalancer. |
125
+
| bitbucket.service.nodePort | string |`nil`| Only applicable if service.type is NodePort. NodePort for Bitbucket service |
125
126
| bitbucket.service.port | int |`80`| The port on which the Bitbucket K8s HTTP Service will listen |
126
127
| bitbucket.service.sessionAffinity | string |`"None"`| Session affinity type. If you want to make sure that connections from a particular client are passed to the same pod each time, set sessionAffinity to ClientIP. See: https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity|
| bitbucket.service.sessionAffinityConfig.clientIP.timeoutSeconds | string |`nil`| Specifies the seconds of ClientIP type session sticky time. The value must be > 0 && <= 86400 (for 1 day) if ServiceAffinity == "ClientIP". Default value is 10800 (for 3 hours). |
130
+
| bitbucket.service.sshNodePort | string |`nil`| SSH Only applicable if service.type is NodePort. NodePort for Bitbucket service |
129
131
| bitbucket.service.sshPort | int |`7999`| The port on which the Bitbucket K8s SSH Service will listen |
130
132
| bitbucket.service.type | string |`"ClusterIP"`| The type of K8s service to use for Bitbucket |
131
133
| bitbucket.setPermissions | bool |`true`| Boolean to define whether to set local home directory permissions on startup of Bitbucket container. Set to 'false' to disable this behaviour. |
132
134
| bitbucket.shutdown.command | string |`"/shutdown-wait.sh"`| By default pods will be stopped via a [preStop hook](https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/), using a script supplied by the Docker image. If any other shutdown behaviour is needed it can be achieved by overriding this value. Note that the shutdown command needs to wait for the application shutdown completely before exiting; see [the default command](https://bitbucket.org/atlassian-docker/docker-atlassian-bitbucket-server/src/master/shutdown-wait.sh) for details. |
133
135
| bitbucket.shutdown.terminationGracePeriodSeconds | int |`35`| The termination grace period for pods during shutdown. This should be set to the Bitbucket internal grace period (default 30 seconds), plus a small buffer to allow the JVM to fully terminate. |
134
-
| bitbucket.sshService | object |`{"annotations":{},"enabled":false,"host":null,"loadBalancerIP":null,"port":22,"type":"LoadBalancer"}`| Enable or disable an additional service for exposing SSH for external access. Disable when the SSH service is exposed through the ingress controller, or enable if the ingress controller does not support TCP. |
136
+
| bitbucket.sshService | object |`{"annotations":{},"enabled":false,"host":null,"loadBalancerIP":null,"nodePort":null,"port":22,"type":"LoadBalancer"}`| Enable or disable an additional service for exposing SSH for external access. Disable when the SSH service is exposed through the ingress controller, or enable if the ingress controller does not support TCP. |
135
137
| bitbucket.sshService.annotations | object |`{}`| Annotations for the SSH service. Useful if a load balancer controller needs extra annotations. |
136
138
| bitbucket.sshService.enabled | bool |`false`| Set to 'true' if an additional SSH Service should be created |
137
139
| bitbucket.sshService.host | string |`nil`| The hostname of the SSH service. If set, it'll be used to configure the SSH base URL for the application. |
138
140
| bitbucket.sshService.loadBalancerIP | string |`nil`| Use specific loadBalancerIP. Only applies to service type LoadBalancer. |
141
+
| bitbucket.sshService.nodePort | string |`nil`| Only applicable if service.type is NodePort. NodePort for Bitbucket ssh service |
139
142
| bitbucket.sshService.port | int |`22`| Port to expose the SSH service on. |
140
143
| bitbucket.sshService.type | string |`"LoadBalancer"`| SSH Service type |
141
144
| bitbucket.startupProbe.enabled | bool |`false`| Whether to apply the startupProbe check to pod. |
Copy file name to clipboardExpand all lines: src/main/charts/confluence/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ Kubernetes: `>=1.21.x-0`
88
88
| confluence.service.annotations | object |`{}`| Additional annotations to apply to the Service |
89
89
| confluence.service.contextPath | string |`nil`| The Tomcat context path that Confluence will use. The ATL_TOMCAT_CONTEXTPATH will be set automatically. |
90
90
| confluence.service.loadBalancerIP | string |`nil`| Use specific loadBalancerIP. Only applies to service type LoadBalancer. |
91
+
| confluence.service.nodePort | string |`nil`| Only applicable if service.type is NodePort. NodePort for Confluence service |
91
92
| confluence.service.port | int |`80`| The port on which the Confluence K8s Service will listen |
92
93
| confluence.service.sessionAffinity | string |`"None"`| Session affinity type. If you want to make sure that connections from a particular client are passed to the same pod each time, set sessionAffinity to ClientIP. See: https://kubernetes.io/docs/reference/networking/virtual-ips/#session-affinity|
| synchrony.service.annotations | object |`{}`| Annotations to apply to Synchrony Service |
225
226
| synchrony.service.loadBalancerIP | string |`nil`| Use specific loadBalancerIP. Only applies to service type LoadBalancer. |
227
+
| synchrony.service.nodePort | string |`nil`| Only applicable if service.type is NodePort. NodePort for Synchrony service |
226
228
| synchrony.service.port | int |`80`| The port on which the Synchrony K8s Service will listen |
227
229
| synchrony.service.type | string |`"ClusterIP"`| The type of K8s service to use for Synchrony |
228
230
| synchrony.setPermissions | bool |`true`| Boolean to define whether to set synchrony home directory permissions on startup of Synchrony container. Set to 'false' to disable this behaviour. |
0 commit comments