Open fredwangwang opened 5 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Need this too. In addition, if gateway api is enabled, some role and rolebinding need to be modified too: https://github.com/search?q=repo%3Acilium%2Fcilium%20gatewayAPI.enabled&type=code
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
What would you like to be added
we are using cilium as CNI and cilium supports Gateway API, which we would like to use.
However, to enable the gateway support, the gateway api CRD must be pre-installed onto the cluster: https://docs.cilium.io/en/latest/network/servicemesh/gateway-api/gateway-api/#prerequisites
this is challenging because when using Kubespray to install the cluster, and CNI, there is no additional steps allowed to pre-install the gateway api before installing the CNI (at least I havent found one..)
The request is to allow installing gateway api crd after the cluster creation to allow seemless integration.
Why is this needed
To make Gateway api available for consumption before installing cilium so that gateway api feature can be enabled directly.