kubernetes-sigs

    kubernetes-sigs/ingress2gateway

    Convert Ingress resources to Gateway API resources

    api
    Go
    Apache-2.0
    1.1K stars
    164 forks
    1.1K GitHub watchers
    Updated Oct 25, 2026
    View on GitHub

    Build with Backblaze B2

    SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.

    Explore Backblaze Labs

    Loading star history...

    Where it stands

    Rank, growth pace and release cadence relative to everything GStars tracks.

    No releases in the last 90 days; the most recent was 111 days ago, with 52 contributors on GitHub.

    Gained 40% fewer stars in the last 90 days than in the 90 days before.

    Use Cases & Benefits

    • Converts Kubernetes Ingress and provider-specific resources into Gateway API resources for standardized API management.
    • Ensures deterministic and conflict-resolved translation of Ingress configurations to Gateway API, supporting multiple providers.
    • Use for migrating legacy Ingress configurations to Gateway API in Kubernetes clusters to leverage modern API gateway features.
    • Use for automating the generation of Gateway and HTTPRoute resources from existing Ingress manifests in CI/CD pipelines.
    • Use for integrating diverse ingress controllers by translating their CRDs into a unified Gateway API format for consistent routing.

    Should you depend on it?

    License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.

    License

    Apache 2.0

    Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.

    Community files

    • README: present
    • Contributing guide: present
    • Code of conduct: present

    Watch-outs

    No watch-outs from GStars' checks.

    General guidance from repository metadata, not legal advice. How we score

    From the README

    Ingress2gateway helps translate Ingress and provider-specific resources (CRDs) to Gateway API resources. Ingress2gateway is managed by the Gateway API SIG-Network subproject.

    Ingress2gateway is primarily focused on translating Ingress and provider-specific resources(CRDs) to Gateway API resources. Widely used provider-specific annotations and/or CRDs may still not be supported. Please refer to supported providers for the current supported providers and their documentation. Contributions for provider-specific annotations and/or CRDs support are mostly welcomed as long as they can be translated to Gateway API directly.

    Note: Ingress2gateway is not intended to copy annotations from Ingress to Gateway API.

    Excerpt from the kubernetes-sigs/ingress2gateway README on GitHub (Apache-2.0 license). © its authors.Read the full README on GitHub

    Daily snapshots

    Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots

    Forks

    164+9

    Open issues

    15-2

    Compared with peers in API

    Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth

    kubernetes-sigs/ingress2gateway compared with API repositories by stars, 7-day star growth, health score and last release
    RepositoryStars+7dHealthLast release
    vxcontrol/pentagi33.5K+7123831 days ago
    usebruno/bruno48.2K+2815914 days ago
    agentgateway/agentgateway6.0K+183609 days ago
    mudler/LocalAI50.2K+1765912 days ago
    sveltejs/svelte88.6K+77659 days ago
    kubernetes-sigs/ingress2gateway1.1K—59111 days ago
    Category median48.2K+18359—

    Also by kubernetes-sigs

    Other repositories from this maintainer that GStars tracks

    Discover Repositories

    Search across tracked repositories by name or description