cluster-api-provider-aws
cluster-api-provider-aws copied to clipboard
[e2e] Add EKS Encryption Test
/kind feature /area provider/eks /area testing /help /priority backlog /milestone v0.7.x
Describe the solution you'd like We need to add an e2e test that covers the EKS encryption functionality. Including enabling encryption to a already created cluster (see #2505 )
Anything else you would like to add:
This is dependent on #2239
Environment:
- Cluster-api-provider-aws version: 0.6.6
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):
@richardcase: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/kind feature /area provider/eks /area testing /help /priority backlog /milestone v0.7.x
Describe the solution you'd like We need to add an e2e test that covers the EKS encryption functionality.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- Cluster-api-provider-aws version: 0.6.6
- Kubernetes version: (use
kubectl version):- OS (e.g. from
/etc/os-release):
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.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/lifecycle frozen
/priority backlog
/remove-lifecycle frozen
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale