(Consider) adoption of `selectableFields`

kubernetes-sigs / gateway-api

Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.

https://gateway-api.sigs.k8s.io

Apache License 2.0

1.83k stars 475 forks source link

(Consider) adoption of `selectableFields` #2862

Open howardjohn opened 7 months ago

howardjohn commented 7 months ago

https://github.com/kubernetes/kubernetes/pull/122717

I would imagine at least Gateway.spec.gatewayClassName and GatewayClass.spec.controllerName could be handy.

For routes probably nothing; parentRef is nice in theory but a controller needs to cleanup if its removed from parentRefs, and parentRef is a struct which makes it infeasible I suspect.

This is alpha in 1.30 so probably this is a very long term change

youngnick commented 7 months ago

That is neat, agreed.

Let's leave this for the stale bot though and unstale as necessary.

k8s-triage-robot commented 4 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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 3 months ago

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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

robscott commented 3 months ago

Assuming we'll need to either wait until 5 trailing versions of Kubernetes support this field or release separate versions of the CRDs for newer Kubernetes versions. In any case, I'm supportive of adding this as soon as it's practical.

/remove-lifecycle rotten

k8s-triage-robot commented 4 weeks 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:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale