-
Notifications
You must be signed in to change notification settings - Fork 268
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
Update README.md - add section about two or more replicas with traefik #492
Conversation
two or more replicas with traefik Signed-off-by: supermario18b <[email protected]>
awesome, thanks for this! I've made the tiniest suggestion and then this can merged :) |
Maybe we should use annotations and write docu for multiple ingress-controller:
Your docu is very traefik specifiy and would be maybe replaced with gateway-api and standard over multiple ingress-controller: |
@wrenix I feel like having a full ingress section of the docs would be nice, and we can certainly approach that later if you'd like, but I think getting this merged is still a good idea in the meantime. In particular, I've seen a lot of hype around the new gateway api (I'm also hyped!), but haven't actually played with it yet. I'd be down for some docs on it as well. |
Signed-off-by: Jesse Hitch <[email protected]>
Sorry, i believe you have miss understand me. The Idea/Reason: An annotation is just a value which has to be set in that helm-chart that is much easier then to deploy an additional manifest (or to put another/not-necessary manifest in that helm-chart. But when the Gateway API is more distributed (as a new standard) then i like the idea to put a "not-necessary Manifest" in a helm-chart. <- this small unimportant sentence was to much present i my last comment) |
@jessebot could we close this PR now? After merge of #621 Or @supermario18b do you like to improve there the traefik section? |
|
Pull Request
Description of the change
It was explained how to create a traefik ingressRoute Resource that uses sticky sessions
Benefits
Users can login when more nextcloud replicas are used
Possible drawbacks
I don't see any
Applicable issues
when more replicas