-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Conversation
548eaba
to
a1f69fa
Compare
a1f69fa
to
373e09d
Compare
373e09d
to
b7e214f
Compare
b7e214f
to
9b8b83b
Compare
This is a very welcome simplification, thank you @wernerb! As the nature of the change isn't backwards-compatible with the current chart, can we please bump the minor semver version? (e.g. to 0.3.0) |
Thanks its bumped. |
The discovery and stun ports are part of the same service. Unifi depends on them to be on the same hostname. Signed-off-by: Werner Buck <email@wernerbuck.nl>
9b8b83b
to
5e1261a
Compare
@wernerb Sorry I didn't address the original question earlier, but agree that a single service for all the things (gui, controller, discovery, stun) makes more sense. Is this something you're willing to include in this PR? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: billimek, wernerb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This merge breaks my UniFi deployment, please see #11268. |
This reverts commit df3b21e.
This reverts commit df3b21e. Signed-off-by: Jeff Billimek <jeff@billimek.com>
The discovery and stun ports are part of the same service. Unifi depends on them to be on the same hostname. Signed-off-by: Werner Buck <email@wernerbuck.nl>
* Revert "Simplify for unifi (helm#10789)" This reverts commit df3b21e. Signed-off-by: Jeff Billimek <jeff@billimek.com> * bumping chart version as part of reversion Signed-off-by: Jeff Billimek <jeff@billimek.com>
What this PR does / why we need it:
This merges the three services into one, letting you have one service (ClusterIP or LoadBalancer, NodePort) that has all ports necessary for proper communication with UAPs.
The problem now is that with each Service you get a different clusterIP (or expensive LoadBalancer) while actually Unifi requires the
8080:/inform
,stun
, anddiscovery
to be on the same interface. (Same as upstream docker).Unifi can't reach stun port right now because its on a different IP, or with NodePort on a different port. NodePort can still work but its also easier through a single service.
Unifi also has no separate IP binding for these ports meaning they are all expected to run off the same IP.
In fact, if the maintainer allows it, we can also remove the controllerService and move everything in one service with multiple named ports.
Signed-off-by: Werner Buck email@wernerbuck.nl
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]