Secrets are always configured

General Discussions
1

Asking for help? Comment out what you need so we can get more information to help you!

Cluster information:

Kubernetes version:
Cloud being used: GCP
Installation method: GCP
Host OS: Linux

I don’t understand why secret are reconfigured even though I’m applying again the same file.

Example:
When I run kustomize build . | kubectl apply -f -, All resources are created.

Once running it again (Didn’t change anything), you can see that secret/init-script-slave is configured.
delete_me

2

Well, have you compared the manifest contents from kustomize build .? I’m betting it’s randomly generating a secret each time.

I doubt customize has a way of knowing the resource already exists. This something like helm provides better tooling to do checks for stuff like that.