Thomas Cardin
Thomas Cardin
We are also facing this similar issue just after installing linkerd.
Hello, thank you for your response, here is the complete setup: Gateway API ```yaml --- apiVersion: gateway.networking.k8s.io/v1 kind: Gateway metadata: name: external-gateway namespace: networking annotations: cert-manager.io/cluster-issuer: letsencrypt-prod spec: gatewayClassName: cilium...
Okay, so if I understand correctly, Cloudflared doesn't need the Gateway API since its tunnel running inside the cluster already allows it to expose a svc to the internet? Still,...
Okay, I've removed the Cloudflared tunnel and configured my system to use a static IP. Now, these commands work as expected (with ports 80 and 443 open on my router)...
Okay, so if I set the IP of my load balancer to my domain name to test locally via /etc/hosts, I get this error on port 443: ```bash curl -vi...
Maybe a cert manager issue? I did enable this feature ` --feature-gates=ExperimentalGatewayAPISupport=true`
Alright, so I think I'm going to close this issue. Everything seems to be working fine since I've been using a static IP. Thanks for your help! I will reopen...
Is there any hotfix for this issue?
I see [here](https://github.com/kubernetes-sigs/azuredisk-csi-driver) that there are several image versions (v1.33.5, v1.32.11, v1.31.12). Should I manage these versions like [aws-ebs-csi-driver.addons.k8s.io](https://github.com/kubernetes/kops/blob/master/upup/models/cloudup/resources/addons/aws-ebs-csi-driver.addons.k8s.io/k8s-1.17.yaml.template#L18) does?