-
Notifications
You must be signed in to change notification settings - Fork 20
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
STOR-860: Rebase to v1.11.4 for OCP 4.12 #206
STOR-860: Rebase to v1.11.4 for OCP 4.12 #206
Conversation
Fix the wrong app and helm chart version
…l_device_resolution Fix canonical nvme device resolution in more cases
Update ECR sidecars to 1-18-13
Set prerelease=true for new releases before images are ready
v1.5.1 post-release
Update cluster role configuration for external snapshotter
Merge release-1.5 to master for v1.5.1
…t and complete changelogs
Add self as OWNER
Signed-off-by: torredil <[email protected]>
…ation-iss21 Update examples/kubernetes README files
Update helm charts for a secrect exposure
This commit fixes the `getVolumesLimit` function. Previously, the volume limit for Nitro instances was based off of a regex. This regex is insufficient for the wide variety of Nitro instances that AWS supports today. Nitro instances share attachments with ENIs and NVMe instance stores. The number of attached ENIs is queried through IMDS, against the `network/interfaces/macs` endpoint. The number of already attached block devices is also queried through IMDS, against the `block-device-mapping` endpoint. Currently, IMDS does not provide a way to query NVMe instance store volumes. So, all instances that support NVMe instance stores are listed in `pkg/cloud/volume_limits.go` This commit also added more tests to cover various scenarios.
Fix nodeService.getVolumesLimit() adding more instance types
Signed-off-by: Eddie Torres <[email protected]>
…ume-id-empty Fix windows mounting bug-1090
Signed-off-by: Gengtao Xu <[email protected]>
Update deprecated command `go get`
Signed-off-by: Eddie Torres <[email protected]>
Platform agnostic device removal
… PodDsruptionBudget
47c1d46
to
e06cb79
Compare
/label docs-approved We don't document / announce CSI driver version bumps to customers. |
8270bb5
to
f16656f
Compare
I finally convinced CI to run |
/lgtm |
Pre verify pass with
The 1 failed is caused by in It seems only a bit strange issue about check the driver version, I'm not sure what causes the driverVersion not as expected by check cmd. It should be
|
f16656f
to
aa945a5
Compare
hack/verify-kustomize reads the current namespace and adds it into generated / verified manifests. With KUBECONFIG="", it won't be able to get the namespace and thus it will generate manifests with namespace: default.
aa945a5
to
f3d2bee
Compare
Removed |
Currently, setting the AWS_EC2_ENDPOINT environment variable overwrites the STS endpoint as well. This patch adds a custom resolver to only set a custom endpoint on EC2 service.
@jsafrane: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
Pre verify pass with
The driverVersion issue fixed, currently there's an upstream issue the
|
/label qe-approved |
/lgtm |
Diff to upstream v1.11.4:
kubernetes-sigs/aws-ebs-csi-driver@v1.11.4...jsafrane:rebase-v1.11.2
Notable changes since v1.5.1 @ 4.11:
vendor/
directory, added it back + updated Makefile to build with-mod=vendor
for offline OCP builds.Full changelog: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/CHANGELOG.md
@openshift/storage