mirror of https://github.com/k3s-io/k3s
e794dce445
Automatic merge from submit-queue AWS: check validity of KSM key before creating a new encrypted disk. AWS CreateVolume call does not check if referenced encryption key actually exists and returns a valid new AWS EBS volume even though an invalid key was specified. Later on it removes the EBS silently when its encryption fails. To work around this buggy behavior we manually check that the key exists before calling CreateVolume. Fixes #48438 /sig aws Please review carefully. Can we safely assume that Kubernetes controller-manager can read encryption keys? ```release-note aws: Kubernetes now checks existence of provided KSM (Key Management Service) key before creating an encrypted AWS EBS. ``` |
||
|---|---|---|
| .. | ||
| bitbucket.org | ||
| cloud.google.com/go | ||
| github.com | ||
| go.pedge.io/pb | ||
| go4.org | ||
| golang.org/x | ||
| google.golang.org | ||
| gopkg.in | ||
| k8s.io | ||
| vbom.ml/util | ||
| BUILD | ||