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

Allow for GatewayRoutes to support setting dualstack annotation #4468

Closed
thameezb opened this issue May 13, 2024 · 2 comments · Fixed by #4469
Closed

Allow for GatewayRoutes to support setting dualstack annotation #4468

thameezb opened this issue May 13, 2024 · 2 comments · Fixed by #4469
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@thameezb
Copy link
Contributor

What would you like to be added:
Similar to ingress and service annotations which specify that AAAA and A records should be created for Dualstack resources, the same feature needs to be available for GatewayRoutes (as in the Gateway API world, a *Route can refers to a Gateway which could be single or dual stack)

Why is this needed:
At the moment for Dualstack gateways, only an A record is created for *Route resources. This breaks compatibility with Ingress migration

@thameezb thameezb added the kind/feature Categorizes issue or PR as related to a new feature. label May 13, 2024
@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 Aug 11, 2024
@thameezb
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 Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants