Source: golang-k8s-sigs-apiserver-network-proxy Section: golang Priority: optional Maintainer: Debian Go Packaging Team Uploaders: Arthur Diniz , Rules-Requires-Root: no Build-Depends: debhelper-compat (= 13), dh-sequence-golang, golang-any, golang-github-google-uuid-dev, golang-github-prometheus-client-model-dev, golang-github-prometheus-common-dev, golang-github-spf13-cobra-dev, golang-github-spf13-pflag-dev, golang-github-stretchr-testify-dev, golang-go.uber-mock-dev, golang-golang-x-net-dev, golang-google-grpc-dev, golang-google-protobuf-dev, golang-k8s-api-dev, golang-k8s-apimachinery-dev, golang-k8s-client-go-dev, golang-k8s-component-base-dev, golang-k8s-component-helpers-dev, golang-k8s-klog-dev, golang-k8s-utils-dev, golang-prometheus-client-dev, golang-uber-goleak-dev, Testsuite: autopkgtest-pkg-go Standards-Version: 4.7.2 Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-k8s-sigs-apiserver-network-proxy Vcs-Git: https://salsa.debian.org/go-team/packages/golang-k8s-sigs-apiserver-network-proxy.git Homepage: https://github.com/kubernetes-sigs/apiserver-network-proxy XS-Go-Import-Path: sigs.k8s.io/apiserver-network-proxy Package: golang-k8s-sigs-apiserver-network-proxy-dev Architecture: all Multi-Arch: foreign Depends: golang-github-google-uuid-dev, golang-github-prometheus-client-model-dev, golang-github-prometheus-common-dev, golang-github-spf13-cobra-dev, golang-github-spf13-pflag-dev, golang-github-stretchr-testify-dev, golang-go.uber-mock-dev, golang-golang-x-net-dev, golang-google-grpc-dev, golang-google-protobuf-dev, golang-k8s-api-dev, golang-k8s-apimachinery-dev, golang-k8s-client-go-dev, golang-k8s-component-base-dev, golang-k8s-component-helpers-dev, golang-k8s-klog-dev, golang-k8s-utils-dev, golang-prometheus-client-dev, golang-uber-goleak-dev, ${misc:Depends}, Description: Proxy server for Kubernetes apiserver network traffic (library) The apiserver-network-proxy is a proxy server designed to facilitate communication between the Kubernetes API server and cluster nodes or components located behind network boundaries, such as firewalls or NATs. . It is commonly used in scenarios like cluster API, edge computing, and multi-tenant environments to securely relay traffic using an agent-server architecture.