Install server instance as a DaemonSet about helm HOT 5 OPEN

Sorry that this is a duplicate of Deployment. I will replace it with a pod template before making a pull request.

Default is server.kind=Deployment. Unless you explicitly set server.kind=DaemonSet, it will behave as before.

Yeah I wasn't really worried about that.

When using Deployment, there is no guarantee that replicas will always be placed on different nodes. I do not want multiple replicas placed on the same node for stable operation.

On the contrary, you can specify affinity and anti-affinity rules so that pods will not end up on the same node: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity. In our helm chart, you can set global.affinity.podAntiAffinity (or override with custom rules in server.affinity and worker.affinity) to soft (the default) so that pods will not end up on the same node or hard so that they don't end up in the same zone: https://github.com/goauthentik/helm/blob/main/charts/authentik/templates/_helpers.tpl#L66.

from helm.

I'm not keen to add another template that's basically a duplicate of what is defined in the deployment one. What's the use case for this?

from helm.

Hi @rissson,

Sorry that this is a duplicate of Deployment. I will replace it with a pod template before making a pull request.

Default is server.kind=Deployment. Unless you explicitly set server.kind=DaemonSet, it will behave as before.

When using Deployment, there is no guarantee that replicas will always be placed on different nodes.
I do not want multiple replicas placed on the same node for stable operation.

from helm.

Thank you for your advice! :)
I'll try using global.affinity.podAntiAffinity

from helm.