Make inlets-operator not fail on existing secret #173
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.
In order for the inlets-operator app to not fail on re-runs
it is necessary for the command to be resilient to the
inlets-access-key secret already being present in cluster.
Signed-off-by: hasheddan georgedanielmangum@gmail.com
Description
Currently, running
k3sup app install inlets-operator
after it has already been run once will fail due to the presence of theinlets-access-key
secret already being present. This change updates behavior to log when the secret is already present, but to continue execution using the existing secret.Motivation and Context
Fixes #172
How Has This Been Tested?
Running installation for the first time on a k3s cluster set up using k3sup:
Running installation for a second time on same k3s cluster:
Note: we still get the
Error from server (AlreadyExists): secrets "inlets-access-key
already exists` printed in output because ofk3sup/cmd/apps/kubernetes_exec.go
Line 240 in 5ce8d6a
Types of changes
Checklist:
git commit -s