# ingress2gateway mit Homebrew, Nix, zypper, winget installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ingress2gateway in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:ingress2gateway ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install ingress2gateway ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#ingress2gateway ``` Evidenz: nixpkgs package indexes: pkgs/by-name/in/ingress2gateway/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - zypper (92%): ```sh sudo zypper install ingress2gateway ``` Evidenz: openSUSE Tumbleweed package metadata: ingress2gateway from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ### Windows - winget (92%): ```sh winget install --id Kubernetes.ingress2gateway -e ``` Evidenz: Windows Package Manager source index: Kubernetes.ingress2gateway from https://cdn.winget.microsoft.com/cache/source.msix ## Paketfakten - **Paketschlüssel:** brew:ingress2gateway - **Paketmanager:** Homebrew - **Version:** 1.2.0 - **Quellzusammenfassung:** Convert Kubernetes Ingress resources to Kubernetes Gateway API resources - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-26T04:07:49+02:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - ingress2gateway (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 1.2.0 ## Projektgeschichte und Nutzung ingress2gateway is a Kubernetes SIG Network tool for translating Kubernetes Ingress and provider-specific resources into Gateway API resources. ### Projektgeschichte The project sits inside kubernetes-sigs and is managed by the Gateway API SIG Network subproject. Its README defines a focused migration scope: read Ingress resources and provider-specific CRDs, convert them into an intermediate representation, and emit Gateway API resources. The changelog records an initial release candidate followed by an official 0.1.0 release, then a steady expansion of providers and conversion behavior. Later releases added APISIX, Istio, GCE, Cilium, NGINX, Traefik, notifications, kyaml output, provider storage, and an emitter framework. ### Adoptionsgeschichte ingress2gateway's adoption follows Kubernetes Gateway API adoption. Teams that accumulated Ingress resources and controller-specific annotations use it to inventory and translate routing configuration while learning which fields and annotations cannot be expressed directly. Package-manager distribution through Homebrew, Nix, Winget, and zypper makes the tool convenient for migration workstations, platform-engineering scripts, and CI checks that inspect manifests without embedding the converter in an application. ### Wie es verwendet wird The primary command reads resources from a cluster through kubeconfig or from YAML/JSON input files, then prints Gateway API YAML, JSON, or kyaml to stdout. Users choose providers such as ingress-nginx, GCE, Istio, Kong, NGINX, Traefik, APISIX, Cilium, or OpenAPI. It does not own credentials files; Kubernetes access follows normal kubeconfig behavior. Its warnings and notifications are part of the migration workflow because unsupported annotations and lossy conversions are often the real work. ### Warum Paket-Nerds sich dafür interessieren ingress2gateway is significant as a transition package: it exists because Kubernetes networking moved from a widely deployed older API to a richer successor API, and the ecosystem needed a CLI bridge. It also turns messy controller-specific annotation culture into explicit provider modules, making package installation a way to audit how portable an ingress estate really is. ### Zeitleiste - 2022: Early project discussion asked for documentation of how Ingress fields and annotations would be interpreted. - 2023: Version 0.1.0-rc1 was tagged as the initial release candidate. - 2024: Version 0.2.0 added providers including Istio and APISIX and moved ingress fetching into provider storage. - 2026: Version 1.0.0 added an emitter framework, expanded ingress-nginx annotation support, and upgraded Gateway API support to v1.5. - 2026: Version 1.1.0 added Traefik provider support and more provider-specific translations. ### Related projects - Related projects include Kubernetes Gateway API, Kubernetes Ingress, ingress-nginx, NGINX Ingress Controller, GKE Gateway, Envoy Gateway, kgateway, agentgateway, APISIX, Cilium, Istio, Kong, and Traefik. ### Quellen - - - - - ## Sicherheitshinweise infrastructure mutation or orchestration signal. - **Geiger-Risiko:** orange / mittel - infrastructure mutation or orchestration signal ## Andere Paketmanager-Einträge - Nix - ingress2gateway: normalized package name match | nixpkgs package indexes: pkgs/by-name/in/ingress2gateway/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - zypper - ingress2gateway - 1.2.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: ingress2gateway from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Convert Ingress resources to Gateway API resources | https://github.com/kubernetes-sigs/ingress2gateway - zypper - ingress2gateway-bash-completion - 1.2.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: ingress2gateway-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Bash Completion for ingress2gateway | https://github.com/kubernetes-sigs/ingress2gateway - zypper - ingress2gateway-fish-completion - 1.2.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: ingress2gateway-fish-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Fish Completion for ingress2gateway | https://github.com/kubernetes-sigs/ingress2gateway - zypper - ingress2gateway-zsh-completion - 1.2.0-1.2: normalized package name match | openSUSE Tumbleweed package metadata: ingress2gateway-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Zsh Completion for ingress2gateway | https://github.com/kubernetes-sigs/ingress2gateway - winget - Kubernetes.ingress2gateway: normalized package name match | Windows Package Manager source index: Kubernetes.ingress2gateway from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/ingress2gateway.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ingress2gateway.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph