From 79674a505669d808faae644134427a4c9eaaed05 Mon Sep 17 00:00:00 2001 From: Drew Sirenko <68304519+AndrewSirenko@users.noreply.github.com> Date: Fri, 20 Dec 2024 11:02:25 -0800 Subject: [PATCH 1/2] test commit --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index ca632cc497..c44674e989 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,9 @@ [![GitHub release (latest SemVer)](https://img.shields.io/github/v/release/kubernetes-sigs/aws-ebs-csi-driver)](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/releases) [![Go Report Card](https://goreportcard.com/badge/github.com/kubernetes-sigs/aws-ebs-csi-driver)](https://goreportcard.com/report/github.com/kubernetes-sigs/aws-ebs-csi-driver) + +TEST LINE + > [!CAUTION] > ## [ACTION REQUIRED] Update to the EBS CSI Driver IAM Policy > Due to an upcoming change in handling of IAM polices for the CreateVolume API when creating a volume from an EBS snapshot, a change to your EBS CSI Driver policy may be needed. For more information and remediation steps, see [GitHub issue #2190](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/2190). From b1b662491d7ac86f3ec55249abde3ec53bb89623 Mon Sep 17 00:00:00 2001 From: Drew Sirenko <68304519+AndrewSirenko@users.noreply.github.com> Date: Fri, 20 Dec 2024 11:12:31 -0800 Subject: [PATCH 2/2] test 2 --- docs/design.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/design.md b/docs/design.md index 96c3ffae29..bd75a37c75 100644 --- a/docs/design.md +++ b/docs/design.md @@ -2,6 +2,8 @@ ## Problems with current in-tree cloud provider ### Cache of used / free device names +TEST LINE + On AWS, it's the client who [must assign device names](https://aws.amazon.com/premiumsupport/knowledge-center/ebs-stuck-attaching/) to volumes when calling AWS.AttachVolume. At the same time, AWS [imposes some restrictions on the device names](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html). Therefore Kubernetes AWS volume plugin maintains cache of used / free device names for each node. This cache is lost when controller-manager process restarts. We try to populate the cache during startup, however there are some corner cases when this fails. TODO: exact flow how we can get wrong cache.