Automic VaultAutomic Vault

brew

ingress2gateway mit Homebrew, Nix, zypper, winget installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für ingress2gateway in AI-Agent-Workflows.

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ingress2gateway

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#ingress2gateway

nixpkgs package indexes · pkgs/by-name/in/ingress2gateway/package.nix · Quelle: api.github.com

openSUSE zypperverifiziert · 92%
sudo zypper install ingress2gateway

openSUSE Tumbleweed package metadata · ingress2gateway · Quelle: download.opensuse.org

Windows

Windows Package Managerverifiziert · 92%
winget install --id Kubernetes.ingress2gateway -e

Windows Package Manager source index · Kubernetes.ingress2gateway · Quelle: cdn.winget.microsoft.com

Überblick

Paketzusammenfassung

Convert Kubernetes Ingress resources to Kubernetes Gateway API resources

Befehle und Aliase

  • ingress2gateway

Verlauf

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.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:kubernetes

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ingress2gatewaycliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-26
Manager-Version1.2.0
Manager aktualisiert2026-07-07
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.2.0

https://github.com/kubernetes-sigs/ingress2gateway

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ingress2gateway
Version1.2.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ingress2gateway
Homepagehttps://github.com/kubernetes-sigs/ingress2gateway
Repositoryhttps://github.com/kubernetes-sigs/ingress2gateway
Upstream-Dokumentationhttps://github.com/kubernetes-sigs/ingress2gateway#readme
LizenzApache-2.0
Quellarchivhttps://github.com/kubernetes-sigs/ingress2gateway/archive/refs/tags/v1.2.0.tar.gz
Zuletzt aktualisiert2026-07-07T21:32:47Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameingress2gateway
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

ingress2gateway

nix profile install nixpkgs#ingress2gateway
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/in/ingress2gateway/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
zypper95%

ingress2gateway 1.1.0-1.1

Convert Ingress resources to Gateway API resources

https://github.com/kubernetes-sigs/ingress2gateway

sudo zypper install ingress2gateway
  • License: Apache-2.0
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: ingress2gateway
  • 1 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: ingress2gateway from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
zypper95%

ingress2gateway-bash-completion 1.1.0-1.1

Bash Completion for ingress2gateway

https://github.com/kubernetes-sigs/ingress2gateway

sudo zypper install ingress2gateway-bash-completion
  • License: Apache-2.0
  • Category: System/Shells
  • Architecture: noarch
  • Source Package: ingress2gateway
  • 2 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: ingress2gateway-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
zypper95%

ingress2gateway-fish-completion 1.1.0-1.1

Fish Completion for ingress2gateway

https://github.com/kubernetes-sigs/ingress2gateway

sudo zypper install ingress2gateway-fish-completion
  • License: Apache-2.0
  • Category: System/Shells
  • Architecture: noarch
  • Source Package: ingress2gateway
  • 2 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: ingress2gateway-fish-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
zypper95%

ingress2gateway-zsh-completion 1.1.0-1.1

Zsh Completion for ingress2gateway

https://github.com/kubernetes-sigs/ingress2gateway

sudo zypper install ingress2gateway-zsh-completion
  • License: Apache-2.0
  • Category: System/Shells
  • Architecture: noarch
  • Source Package: ingress2gateway
  • 2 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
openSUSE Tumbleweed package metadata · download.opensuse.org · openSUSE Tumbleweed package metadata: ingress2gateway-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/be8d3611d25469107f32075a1697e69ec57a2b850b42348a658cc671ad5ec2b50760d02c3e59524d50da9a11d5be799bdaffba2e166e8ca8858512e3c0bd665d-primary.xml.zst
winget95%

Kubernetes.ingress2gateway

winget install --id Kubernetes.ingress2gateway -e
  • normalized package name match
  • Abgeglichen nach: Ingress2gateway
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Kubernetes.ingress2gateway from https://cdn.winget.microsoft.com/cache/source.msix

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Verwandte Tools

  • goBuild dependency declared by Homebrew.

Gleicher Workflow

  • cloud-provider-kindShares av.db curated category or tags: cli, cloud-infrastructure, gateway-api, kubernetes.
  • egctlShares av.db curated category or tags: cli, cloud-infrastructure, gateway-api, kubernetes.
  • gwctlShares av.db curated category or tags: cli, cloud-infrastructure, gateway-api, kubernetes.
  • veleroShares av.db curated category or tags: cli, cloud-infrastructure, kubernetes, migration.
  • argoShares av.db curated category or tags: cli, cloud-infrastructure, kubernetes.
  • argocdShares av.db curated category or tags: cli, cloud-infrastructure, kubernetes.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment