MatthieuFin
MatthieuFin
Yes, I think you didn't create appropriate secret to reference you Global section "region-1" Create following secret in kube-system namespace: ```yaml apiVersion: v1 stringData: cloud: region-1 kind: Secret metadata: name:...
Hi this version is deployed on our cluster from a couple of weeks it seems to be stable. @dulek @mdbooth @jichenjc @kayrus Please take a look.
Sorry for latency, I had some emergencies to resolved first. @dulek thanks for your review I tried to answer to your questions and made changes requested. I will look to...
Thanks to @sebastienmusso, @fllaap and @Krast76 who offered to help write documentation. @dulek, @jichenjc, @kayrus, @mdbooth how can we advance this PR ?
Hi @jichenjc , Other cloud provider (I'll take example of GCP) offer a unique storage class which is able to create pods across multiple "regions". To do that they implements...
I agree, support for VOLUME_ACCESSIBILITY_CONSTRAINTS capability should be compatible with this multi-cloud PR implementation. If anyone has access to a multi-AZ openstack cluster :crossed_fingers: . I intentionally let the user...
Anyone to made this PR https://github.com/kubernetes/cloud-provider-openstack/pull/2551 move forward ?
Hello, I have the habit of managing the deployment of calico with kubespray. I suffered 2 outages due to this issue, the first was to change the requested resources of...
Hi, yes I tested the changes, that's the workaround that I use on my production clusters. I have also tested them on new fresh cluster creation and they seem fully...