Closed dulmandakh closed 2 weeks ago
Hey @dulmandakh ,
Thank you for reporting this issue. This seems like a bug. ck-gateway
is the class managed by the k8s-snap
and should be the default, it seems that cilium also creates a gateway class automatically which is unintentional.
I'll raise a PR and keep updating here, thanks!
Summary
I see 2 same GatewayClass resources when I enter below command, except helm install name and namespace. We would need some explanation about propose of having 2
GatewayClass
es.One in
kube-system
namespaceAnother in
default
namespaceWhat Should Happen Instead?
I expect to see one or default gatewayclass.
Reproduction Steps
kubectl get gatewayclass -o yaml
commandGatewayClass
esSystem information
inspection-report-20250422_012741.tar.gz
Can you suggest a fix?
Add more documentation about Gateway and explain if there is a distinction.
Are you interested in contributing with a fix?
No response