Raphael

@revolunet If the region supports it you can add a storage class yourself : ``` apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: csi-cinder-high-speed-gen2 parameters: availability: nova fsType: ext4 type: high-speed-gen2 allowVolumeExpansion:...

IOPS scales up based on capacity, try instancing a 100Gi or 300Gi volume to see how it goes

To clarify : the policy works but it happens to log a lot of errors while it's being applied hourly. The background controller has permission to update Namespaces (helm values)...

Until there is a better solution we "solved" it with a kubernetes probe : ```yaml apiVersion: apps/v1 kind: Deployment [...] spec: containers: - env: - name: SEMAPHORE_API_TOKEN valueFrom: secretKeyRef: key:...

The page for Account and Password also looks completely different from what Keycloak has : 

Same issue on 2.6.0

Assuming a brand new deployment and all clients running 0.29+ where does coturn fit in the picture ? Can we just run coturn with `--stun-only` if retrocompability is no concern...

linkerd seems to look for a specific version of the CRDs in linkerd-destination/policy container when I tried with gateway [1.1](https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.1.0/standard-install.yaml) : ``` 2024-09-23T08:56:29.231903Z WARN kube_client::client: Unsuccessful data error parse: 404...

[A merge request was created](https://github.com/traefik/traefik-helm-chart/pull/1223) on the helm repo to separate traefik and its CRDs into separate charts with the ability to disable the Gateway CRDs so that should help...