-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for GA/1.0.0 release of the Kubernetes Gateway API - gateway.networking.k8s.io/v1 #2854
Comments
Thanks for pointing this out @tedvanderveen; we'll try to get this on the roadmap. |
Thanks for putting it on the roadmap @mjeffryes. Please be aware that this missing k8s API support is currently blocking effective usage of quite a few implementation already using it: see https://gateway-api.sigs.k8s.io/implementations |
@tedvanderveen As we consider incorporating these add-on resources into the Pulumi Kubernetes provider, you have the option to utilize crd2pulumi for generating typed resources corresponding to the desired Gateway API CRDs. This approach would enable you to access the status subresources of the Gateway API CRs as a workaround. |
Thanks for the hint, @rquitales . Unfortunately, when I run the command
Am I using the tool wrong? The YAML file is the one from https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.0.0/standard-install.yaml. |
OK, I see there's an issue for it pulumi/crd2pulumi#61 |
Hello!
Issue details
The first GA version of the k8s Gateway API was released 4 months ago: https://github.com/kubernetes-sigs/gateway-api/releases/tag/v1.0.0. Sounds like the right time to add support for this API.
At the moment, when using the k8s
@pulumi/kubernetes/apiextensions/customResource
class, there is no means of accessing for example thestatus
field of the Gateway, or the FQDN assigned by the implementation (available via.status.addresses[0].value
).Affected area/feature
The text was updated successfully, but these errors were encountered: