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

Infrastructure Provider Guidance #3709

Open
shaneutt opened this issue Mar 25, 2025 · 0 comments
Open

Infrastructure Provider Guidance #3709

shaneutt opened this issue Mar 25, 2025 · 0 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@shaneutt
Copy link
Member

Historically, Gateway API has focused on cluster operators and developers, with less emphasis on the infrastructure provider role. Now that Gateway API is GA and integrated into many platforms (often by default), there is a lack of documentation and guidance for those infrastructure providers to follow.

This task aims to create clear guidance for the infrastructure provider role, including:

  • Managing the life-cycle of Gateway API CRDs and delivering Gateway API as a core component
  • Safely supporting multiple Gateway API implementations on the same cluster

This will help ensure a consistent Gateway API experience across different platforms.

@shaneutt shaneutt added kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 25, 2025
@shaneutt shaneutt moved this to Triage in Gateway API Pipeline Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: Triage
Development

No branches or pull requests

1 participant