gateway-api icon indicating copy to clipboard operation
gateway-api copied to clipboard

(Consider) adoption of `selectableFields`

Open howardjohn opened this issue 2 years ago • 5 comments

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

howardjohn avatar Mar 11 '24 15:03 howardjohn

That is neat, agreed.

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

youngnick avatar Mar 12 '24 04:03 youngnick

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 avatar Jun 10 '24 04:06 k8s-triage-robot

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

k8s-triage-robot avatar Jul 10 '24 04:07 k8s-triage-robot

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

robscott avatar Jul 10 '24 23:07 robscott

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 avatar Oct 09 '24 00:10 k8s-triage-robot

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

k8s-triage-robot avatar Nov 08 '24 01:11 k8s-triage-robot

/remove-lifecycle stale /lifecycle frozen

youngnick avatar Nov 08 '24 04:11 youngnick

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 avatar May 12 '25 18:05 k8s-triage-robot

This was frozen because it is blocked by upstream.

/remove-lifecycle stale /lifecycle frozen

youngnick avatar May 13 '25 04:05 youngnick