[cinder-csi-plugin] Multi-region support for provisioning Cinder storage. #2035

albgus · 2022-11-16T13:16:29Z

/kind feature

I have a scenario where we would need to implement high-availability across two datacenters, each operating as their own OpenStack region. As both regions are in the same City with a high speed low latency (<1ms) network between then it would be possible to create a stretched cluster between the regions. (I'm aware it's not possible to create proper high-availability of etcd with just two regions, but I belive it can be managed and it's a separate issue).

We do have some components that need persistent storage in our cluster, and we would like to be able to deploy these components in Kubernetes and use the built-in region awareness to deploy apps and their volumes.

Seems it should be possible to label each node with an appropriate topology.kubernetes.io/region label and then configure the Cinder CSI to map regions to a set of OpenStack credentials. Then get kind of similar to how for example the AWS EBS CSI manages different availability zones, with the awareness that only nodes in the correct region will be able to mount the volumes.

This might be a duplicate of #1924 , but I only really care about the storage part, we wouldn't need for instance the LoadBalancer support.

The text was updated successfully, but these errors were encountered:

jichenjc · 2022-11-18T04:05:39Z

OpenStack region

openstack region concept is multiple openstack cluster running and share keystone / horizon
I think you are talking about AZ, which you mihgt refer to
ignore-volume-az key word at https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/cinder-csi-plugin/using-cinder-csi-plugin.md

albgus · 2022-11-18T08:59:27Z

No, I'm specifically talking about region. It would be really nice if OpenStack providers has their shit together at the same level as AWS, GCP, etc.. But it seems more common than not that providers chose to deploy separate regions in the same area as opposed to deploying a big OpenStack cloud with proper availability zones set up. Due to this I think it would be good if the Cinder CSI driver would work with this scenario. In my case there is no shared keystone either, presumably to fault isolate the regions or something..

At the very least OVH and Hetzner has this availability zone less setup, and it seems more common than not with public providers and I'm guessing the same may be true for many privately hosted setups.

cambierr · 2022-12-13T13:45:28Z

I'm guessing the same may be true for many privately hosted setups.

Can confirm with ~ 10 of our private clusters

jichenjc · 2022-12-15T01:31:14Z

Seems it should be possible to label each node with an appropriate topology.kubernetes.io/region label and then configure the Cinder CSI to map regions to a set of OpenStack credentials.

ok, this make sense, some thoughts:

we support multiple cloud definition so this should be good
we should be able to pass region param in controllerServer.CreateVolume
with 1) 2), we are able to talk to different region to create volume
during attachment, need more time to know how to find corresponding node to do the attachment (e.g same region )

as I don't have those env ,so I am happy to get someone cooperate on this topic if you like , thanks

cambierr · 2022-12-15T11:31:50Z

I wrote such a MVP implementation about 1yeat ago but the PR never got reviewed. If there is more interest in this now, I'd be happy to rebase and re-submit a PR. Sent from a typical smartphone. If this is illiterate, it’s the voice recognition’s fault.

…

________________________________ From: ji chen ***@***.***> Sent: Thursday, December 15, 2022 2:31:24 AM To: kubernetes/cloud-provider-openstack ***@***.***> Cc: Romain Cambier ***@***.***>; Comment ***@***.***> Subject: Re: [kubernetes/cloud-provider-openstack] [cinder-csi-plugin] Multi-region support for provisioning Cinder storage. (Issue #2035) Seems it should be possible to label each node with an appropriate topology.kubernetes.io/region label and then configure the Cinder CSI to map regions to a set of OpenStack credentials. ok, this make sense, some thoughts: 1. we support multiple cloud definition so this should be good 2. we should be able to pass region param in controllerServer.CreateVolume 3. with 1) 2), we are able to talk to different region to create volume 4. during attachment, need more time to know how to find corresponding node to do the attachment (e.g same region ) as I don't have those env ,so I am happy to get someone cooperate on this topic if you like , thanks — Reply to this email directly, view it on GitHub<#2035 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACTBVYZ4NTQVRPJ5PNWVZL3WNJYGZANCNFSM6AAAAAASCG7TCI>. You are receiving this because you commented.Message ID: ***@***.***>

jichenjc · 2022-12-16T00:48:39Z

please resubmit so at least I an help review , thanks for the feedback~

jichenjc · 2023-01-30T03:05:12Z

@cambierr could you please help submit? Thanks

k8s-triage-robot · 2023-04-30T03:25:50Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2023-05-30T03:46:22Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot · 2023-06-29T04:17:19Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot · 2023-06-29T04:17:24Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

jichenjc · 2023-06-29T04:18:48Z

/reopen

k8s-ci-robot · 2023-06-29T04:18:53Z

@jichenjc: Reopened this issue.

In response to this:

/reopen

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.

k8s-triage-robot · 2024-01-19T05:00:16Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot · 2024-01-19T05:00:22Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

dulek · 2024-01-19T14:23:38Z

/reopen

This seems to be a sane thing.

k8s-triage-robot · 2024-02-18T14:58:17Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot · 2024-02-18T14:58:22Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.

MatthieuFin · 2024-02-19T20:05:56Z

/reopen

k8s-ci-robot · 2024-02-19T20:05:59Z

@MatthieuFin: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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.

…ubernetes#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]>

dulek · 2024-02-28T17:29:25Z

/remove-lifecycle rotten

dulek · 2024-02-28T17:29:36Z

/remove-lifecycle stale

…ubernetes#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]>

k8s-triage-robot · 2024-05-28T18:09:02Z

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot · 2024-06-27T18:32:29Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

MatthieuFin · 2024-06-27T19:42:18Z

Anyone to made this PR #2551 move forward ?

…ubernetes#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]>

…ubernetes#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]>

k8s-triage-robot · 2024-07-27T19:51:36Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot · 2024-07-27T19:51:40Z

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.

devfaz · 2024-07-29T12:22:50Z

/reopen

k8s-ci-robot · 2024-07-29T12:22:54Z

@devfaz: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

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-sigs/prow repository.

…2551) * feat(cinder-csi-plugin): add support multi cloud openstack cluster (#2035) * feat(cinder-csi-plugin-controller): add support --cloud-name arg which permit to manage multiple config Global sections * feat(cinder-csi-plugin-controller): add support of key `cloud` from secret specified in storageClass to reference specific config Global section * feat(cinder-csi-plugin-node): add support --cloud-name arg which permit to specify one of config Global section Signed-off-by: MatthieuFin <[email protected]> * feat(cinder-csi-plugin): add possibility to set custom topology keys (#2035) * feat(cinder-csi-plugin-node): Additionnal topology keys `--additionnal-topology` are announced on NodeGetInfo to create proper CSINode object and could used in storage class allowedTopologies field, in combination with csi-provisioner `--feature-gates Topology=true` created PV will have nodeAffinity set with topologies presents in storageClass allowedTopologies and in `--additionnal-topology` argument. Signed-off-by: MatthieuFin <[email protected]> * refactor: 💡 rephrase command flags descriptions Signed-off-by: MatthieuFin <[email protected]> * refactor: 💡 remove useless declaration * refactor: 💡 loop with range instead of C like * docs(cinder-csi-plugin): multi cloud configuration add documentation and examples about multi cloud support configuration Co-authored-by: sebastienmusso <[email protected]> Co-authored-by: FlorentLaloup <[email protected]> Signed-off-by: MatthieuFin <[email protected]> * fix(cinder-csi-plugin): controllerServer ListVolumes with `--max-entries` arg Add unit tests cases on listvolumes function in multicloud configuration with and without `--max-entries` arg Signed-off-by: MatthieuFin <[email protected]> --------- Signed-off-by: MatthieuFin <[email protected]> Co-authored-by: sebastienmusso <[email protected]> Co-authored-by: FlorentLaloup <[email protected]>

k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 16, 2022

jichenjc mentioned this issue Dec 15, 2022

[cinder-csi-plugin] Multiple Openstack Cluster Handling #2056

Closed

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 30, 2023

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 30, 2023

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 29, 2023

k8s-ci-robot reopened this Jun 29, 2023

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2024

dulek reopened this Jan 19, 2024

MatthieuFin mentioned this issue Feb 14, 2024

[cinder-csi-plugin] Multi region/clouds support for controllerServer #2551

Merged

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 18, 2024

dulek reopened this Feb 28, 2024

k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 28, 2024

sergelogvinov mentioned this issue May 16, 2024

[cinder-csi-plugin] csi-cinder storage capacity #2597

Draft

k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 28, 2024

k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 27, 2024

k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2024

k8s-ci-robot closed this as completed in #2551 Jul 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[cinder-csi-plugin] Multi-region support for provisioning Cinder storage. #2035

[cinder-csi-plugin] Multi-region support for provisioning Cinder storage. #2035

albgus commented Nov 16, 2022

jichenjc commented Nov 18, 2022

albgus commented Nov 18, 2022

cambierr commented Dec 13, 2022

jichenjc commented Dec 15, 2022

cambierr commented Dec 15, 2022 via email

jichenjc commented Dec 16, 2022

jichenjc commented Jan 30, 2023

k8s-triage-robot commented Apr 30, 2023

k8s-triage-robot commented May 30, 2023

k8s-triage-robot commented Jun 29, 2023

k8s-ci-robot commented Jun 29, 2023

jichenjc commented Jun 29, 2023

k8s-ci-robot commented Jun 29, 2023

k8s-triage-robot commented Jan 19, 2024

k8s-ci-robot commented Jan 19, 2024

dulek commented Jan 19, 2024

k8s-triage-robot commented Feb 18, 2024

k8s-ci-robot commented Feb 18, 2024

MatthieuFin commented Feb 19, 2024

k8s-ci-robot commented Feb 19, 2024

dulek commented Feb 28, 2024

dulek commented Feb 28, 2024

k8s-triage-robot commented May 28, 2024

k8s-triage-robot commented Jun 27, 2024

MatthieuFin commented Jun 27, 2024

k8s-triage-robot commented Jul 27, 2024

k8s-ci-robot commented Jul 27, 2024

devfaz commented Jul 29, 2024

k8s-ci-robot commented Jul 29, 2024

[cinder-csi-plugin] Multi-region support for provisioning Cinder storage. #2035

[cinder-csi-plugin] Multi-region support for provisioning Cinder storage. #2035

Comments

albgus commented Nov 16, 2022

jichenjc commented Nov 18, 2022

albgus commented Nov 18, 2022

cambierr commented Dec 13, 2022

jichenjc commented Dec 15, 2022

cambierr commented Dec 15, 2022 via email

jichenjc commented Dec 16, 2022

jichenjc commented Jan 30, 2023

k8s-triage-robot commented Apr 30, 2023

k8s-triage-robot commented May 30, 2023

k8s-triage-robot commented Jun 29, 2023

k8s-ci-robot commented Jun 29, 2023

jichenjc commented Jun 29, 2023

k8s-ci-robot commented Jun 29, 2023

k8s-triage-robot commented Jan 19, 2024

k8s-ci-robot commented Jan 19, 2024

dulek commented Jan 19, 2024

k8s-triage-robot commented Feb 18, 2024

k8s-ci-robot commented Feb 18, 2024

MatthieuFin commented Feb 19, 2024

k8s-ci-robot commented Feb 19, 2024

dulek commented Feb 28, 2024

dulek commented Feb 28, 2024

k8s-triage-robot commented May 28, 2024

k8s-triage-robot commented Jun 27, 2024

MatthieuFin commented Jun 27, 2024

k8s-triage-robot commented Jul 27, 2024

k8s-ci-robot commented Jul 27, 2024

devfaz commented Jul 29, 2024

k8s-ci-robot commented Jul 29, 2024