-
Notifications
You must be signed in to change notification settings - Fork 43
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
Encrypted ebs volumes #156
Conversation
/hold |
/retest |
/test e2e |
1 similar comment
/test e2e |
/retest |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing 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 |
/test e2e-aws |
c7df773
to
3726ece
Compare
/test e2e-aws |
All of this din't make any sense, root EBS volumes are either encrypted when the AMI is private and encrypted or not if they're public or not encrypted. |
@spangenberg: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
- Add cluster-api-provider-aws specific tag - Add name tags to resources we create - handle terminated instances for bastion - attempt to avoid orphaning eips when NAT gateway creation fails
No description provided.