-
Notifications
You must be signed in to change notification settings - Fork 269
Application-layer new-cluster automation #6226
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
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ralphbean The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The API isn't giving the response I expected.
I want it to be able to run with --tags vault and have that make sense.
@ralphbean If you're referring to kms key for the velero backup in the description of this PR, we will not use that anymore for new environments as we're creating s3 bucket (for velero backup) using the default s3 encryption managed by aws itself. We can always change that if we need to and change terraform module to create kms key for the velero backup. |
One thing that's up in the air here is dealing with the valero backup key. I assume that is waiting on some new work to be done in the cluster-level automation and can be followed up on later.