feat: make aws credentials optional when s3 backup #552
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.
What this PR does / why we need it*:
The
S3CredentialSecret
field inServerConfig.Etcd.BackupConfig.S3.S3CredentialSecret
is required and limits users to authenticate with AWS access/secret keys only. Making this optional allows using assumed IAM roles instead.When setting
ServerConfig
, it will now check if the value is empty and ignore it, so it does not trigger a controller error. Even though this is not required, users are expected to set this if they need to use access/secret key authentication. Controller behavior should not be changed if user provides a validS3CredentialSecret
value.Which issue(s) this PR fixes:
Fixes #512
Special notes for your reviewer:
Checklist: