-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add serviceName to NFS StatefulSet #229
base: release/kubernetes-agent/v1
Are you sure you want to change the base?
Add serviceName to NFS StatefulSet #229
Conversation
🦋 Changeset detectedLatest commit: 2f9fc57 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for adding an install test as well for the current version.
The only thing I'm not certain of is whether this now breaks installation via ArgoCD, since I'm not certain if argo works with lookup
functions (see argoproj/argo-cd#5202)
Converting back to draft as we may not want to actually merge this change |
When using a
StatefulSet
with a headless service, you are supposed to set thespec.serviceName
value. We weren't.However, once a stateful set is created, this value can't be modified.
Because the
serviceName
can't be modified after creation (even on an upgrade), we only include the service name if the statefulset doesn't exist, or if the statefulset exists and the serviceName is defined.Not setting this value isn't a big issue because we don't have multiple replica's of the NFS pods