Andrei Kvapil
798b5c9f2a
* Add missing steps to configure konnectivity-server * Update content/en/docs/tasks/extend-kubernetes/setup-konnectivity.md Co-authored-by: Tim Bannister <tim@scalefactory.com> * Update content/en/docs/tasks/extend-kubernetes/setup-konnectivity.md Co-authored-by: Tim Bannister <tim@scalefactory.com> * Update content/en/docs/tasks/extend-kubernetes/setup-konnectivity.md Co-authored-by: Tim Bannister <tim@scalefactory.com> * update konnectivity manifests * remove tcp configuration Co-authored-by: Tim Bannister <tim@scalefactory.com>
22 lines
1.1 KiB
YAML
22 lines
1.1 KiB
YAML
apiVersion: apiserver.k8s.io/v1beta1
|
|
kind: EgressSelectorConfiguration
|
|
egressSelections:
|
|
# Since we want to control the egress traffic to the cluster, we use the
|
|
# "cluster" as the name. Other supported values are "etcd", and "master".
|
|
- name: cluster
|
|
connection:
|
|
# This controls the protocol between the API Server and the Konnectivity
|
|
# server. Supported values are "GRPC" and "HTTPConnect". There is no
|
|
# end user visible difference between the two modes. You need to set the
|
|
# Konnectivity server to work in the same mode.
|
|
proxyProtocol: GRPC
|
|
transport:
|
|
# This controls what transport the API Server uses to communicate with the
|
|
# Konnectivity server. UDS is recommended if the Konnectivity server
|
|
# locates on the same machine as the API Server. You need to configure the
|
|
# Konnectivity server to listen on the same UDS socket.
|
|
# The other supported transport is "tcp". You will need to set up TLS
|
|
# config to secure the TCP transport.
|
|
uds:
|
|
udsName: /etc/kubernetes/konnectivity-server/konnectivity-server.socket
|