@@ -53,20 +53,8 @@ The following tables lists the configurable parameters of the Unifi chart and th
53
53
| ` controllerService.loadBalancerIP ` | Loadbalance IP for the Unifi Controller | ` {} ` |
54
54
| ` controllerService.loadBalancerSourceRanges ` | List of IP CIDRs allowed access to load balancer (if supported) | None |
55
55
| ` controllerService.externalTrafficPolicy ` | Set the externalTrafficPolicy in the Service to either Cluster or Local | ` Cluster ` |
56
- | ` stunService.type ` | Kubernetes service type for the Unifi STUN | ` NodePort ` |
57
- | ` stunService.port ` | Kubernetes UDP port where the Unifi STUN is exposed | ` 3478 ` |
58
- | ` stunService.annotations ` | Service annotations for the Unifi STUN | ` {} ` |
59
- | ` stunService.labels ` | Custom labels | ` {} ` |
60
- | ` stunService.loadBalancerIP ` | Loadbalance IP for the Unifi STUN | ` {} ` |
61
- | ` stunService.loadBalancerSourceRanges ` | List of IP CIDRs allowed access to load balancer (if supported) | None |
62
- | ` stunService.externalTrafficPolicy ` | Set the externalTrafficPolicy in the Service to either Cluster or Local | ` Cluster ` |
63
- | ` discoveryService.type ` | Kubernetes service type for AP discovery | ` NodePort ` |
64
- | ` discoveryService.port ` | Kubernetes UDP port for AP discovery | ` 10001 ` |
65
- | ` discoveryService.annotations ` | Service annotations for AP discovery | ` {} ` |
66
- | ` discoveryService.labels ` | Custom labels | ` {} ` |
67
- | ` discoveryService.loadBalancerIP ` | Loadbalance IP for AP discovery | ` {} ` |
68
- | ` discoveryService.loadBalancerSourceRanges ` | List of IP CIDRs allowed access to load balancer (if supported) | None |
69
- | ` discoveryService.externalTrafficPolicy ` | Set the externalTrafficPolicy in the Service to either Cluster or Local | ` Cluster ` |
56
+ | ` controllerService.stun.port ` | Kubernetes UDP port where the Unifi STUN is exposed | ` 3478 ` |
57
+ | ` controllerService.discovery.port ` | Kubernetes UDP port for AP discovery | ` 10001 ` |
70
58
| ` ingress.enabled ` | Enables Ingress | ` false ` |
71
59
| ` ingress.annotations ` | Ingress annotations | ` {} ` |
72
60
| ` ingress.labels ` | Custom labels | ` {} ` |
@@ -117,12 +105,12 @@ Read through the [values.yaml](values.yaml) file. It has several commented out s
117
105
devices run. If you run this as a ` NodePort ` (the default setting), make sure
118
106
that there is an external load balancer that is directing traffic from port
119
107
8080 to the ` NodePort ` for this service.
120
- - ` discoveryService ` : This needs to be reachable by the unifi devices on the
121
- network similar to the controller ` Service ` but only during the discovery
122
- phase. This is a UDP service.
123
- - ` stunService ` : Also used periodically by the unifi devices to communicate
124
- with the controller using UDP. See [ this article ] [ ubnt 3 ] and [ this other
125
- article] [ ubnt 4 ] for more information.
108
+
109
+ the ` controllerService ` exposes two additional ports:
110
+ - ` discovery ` : This needs to be reachable by the unifi devices on network but only during the discovery
111
+ phase. This is a UDP service.
112
+ - ` stun ` : Also used periodically by the unifi devices to communicate
113
+ with the controller using UDP. See [ this article ] [ ubnt 3 ] and [ this other article] [ ubnt 4 ] for more information.
126
114
127
115
[ docker ] : https://hub.docker.com/r/jacobalberty/unifi/tags/
128
116
[ github ] : https://github.com/jacobalberty/unifi-docker
0 commit comments