Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a GatewayClass SupportedVersion Status Condition Test #3367

Open
danehans opened this issue Sep 27, 2024 · 3 comments · May be fixed by #3368
Open

Add a GatewayClass SupportedVersion Status Condition Test #3367

danehans opened this issue Sep 27, 2024 · 3 comments · May be fixed by #3368
Assignees

Comments

@danehans
Copy link
Contributor

What would you like to be added:
A conformance test for the GatewayClass SupportedVersion status condition.

Why this is needed:
The v1.0.0 release added the SupportedVersion status condition to the GatewayClass type.

@danehans
Copy link
Contributor Author

/assign

danehans added a commit to danehans/gateway-api that referenced this issue Sep 27, 2024
Adds a test to ensure implementations conform to the GatewayClass
SupportedVersion status condition.

Fixes kubernetes-sigs#3367

Signed-off-by: Daneyon Hansen <[email protected]>
danehans added a commit to danehans/gateway-api that referenced this issue Sep 27, 2024
Adds a test to ensure implementations conform to the GatewayClass
SupportedVersion status condition.

Fixes kubernetes-sigs#3367

Signed-off-by: Daneyon Hansen <[email protected]>
danehans added a commit to danehans/gateway-api that referenced this issue Sep 27, 2024
Adds a test to ensure implementations conform to the GatewayClass
SupportedVersion status condition.

Fixes kubernetes-sigs#3367

Signed-off-by: Daneyon Hansen <[email protected]>
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 26, 2024
@danehans
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants