Open bokjo opened 8 months ago
@spencerhance & @robscott can you relate to this issue? What it takes to support this, maybe one of the members from the community can pick it up?
Some initial thoughts...
The following GCP-specific stuff can be implemented fairly easily (not an exhaustive list):
kubernetes.io/ingress.class
-> Gateway Classkubernetes.io/ingress.global-static-ip-name
-> Gateway NamedAddress
kubernetes.io/ingress.global-static-ip-name
-> Gateway NamedAddress
ingress.gcp.kubernetes.io/pre-shared-cert
-> Gateway TLS option networking.gke.io/pre-shared-certs
The other features require converting the FrontendConfig and BackendConfig CRDs to ServicePolicies. FC/BC are located in Ingress-gce and can be imported here. The ServicePolicy YAMLs are exported in gateway-api/config/servicepolicies/crd but we would have to export the go types as well so we can use the controller runtime client here.
I can definitely assist here (especially with the ServicePolicies).
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
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
Hi @LiorLieberman I've talked to Rob, and I would like to work on this.
/assign
/remove-lifecycle rotten
Hey @sawsa307, thats awesome! Let me know if I can help with anything!
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
/remove-lifecycle stale
What would you like to be added: support for the GCE ingress provider
Why this is needed: to convert existing GCE ingress to the new GW API
Error while executing
the current ingress has the following YAML (Redacted info)