fix: don't set empty image pull secrets #936
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary Of Changes
commit "5f98b43" added the ability to set image pull secrets from the
DEFAULT_IMAGE_PULL_SECRETS env var.
5f98b43
In the case where the
DEFAULT_IMAGE_PULL_SECRETS
env var is unset,DefaultImagePullSecrets
will be""
, andstrings.Split(r.DefaultImagePullSecrets, ",")
will return an array of length one containing an empty string and an image pull secret will be created with an empty string. This commit adds check to the output ofstrings.Split()
to ensure we don't set an empty strings.When this empty string is saved and parsed by k8s, resulting operations get this error:
you can also see the problem here:
Additional Context
Local Testing
Please ensure you run the unit, integration and system tests before approving the PR.
To run the unit and integration tests:
You will need to target a k8s cluster and have the operator deployed for running the system tests.
For example, for a Kubernetes context named
dev-bunny
: