kubeadm-init-phase-addon-kube-proxy1
Install the kube-proxy addon to a kubernetes cluster
Usage
kubeadm init phase addon kube-proxy [OPTIONS]
Eric Paris Jan 2015
Overview
Install the kube-proxy addon components via the API server.
Options
--apiserver-advertise-address=""
The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
--apiserver-bind-port=6443
Port for the API Server to bind to.
--config=""
Path to a kubeadm configuration file.
--control-plane-endpoint=""
Specify a stable IP address or DNS name for the control plane.
--dry-run=false
Don't apply any changes; just output what would be done.
--image-repository="registry.k8s.io"
Choose a container registry to pull control plane images from
--kubeconfig="/etc/kubernetes/admin.conf"
The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.
--kubernetes-version="stable-1"
Choose a specific Kubernetes version for the control plane.
--pod-network-cidr=""
Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
--print-manifest=false
Print the addon manifests to STDOUT instead of installing them
Options inherited from parent commands
--rootfs=""
The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.
--version=false
--version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version