ETCD access to the API server

The following flags should be set in the ETCD yaml:



--peer-key-file=<path to peerkey>/peer.key

--peer-cert-file=<path to peercert>/peer.crt

--key-file=<path to serverkey>/server.key

--cert-file=<path to servercert>/server.crt

--trusted-ca-file=<path to cacert>/ca.crt

Like in the API-SERVER yaml:

--etcd-cafile=<path from the --trusted-ca-file and --peer-trusted-ca-file in the ETCD yaml>.

--etcd-keyfile=<path to apikey>/apiserver-etcd-client.key

--etcd-certfile=<path to apicert>/apiserver-etcd-client.crt

Any Questions?

Please feel free to contact us for any question that is not answered yet. 

We are looking forward to get in contact with you!

Design Escapes

KubeOps GmbH
Hinter Stöck 17
72406 Bisingen

  • Telefon:

    +49 7433 93724 90

  • Mail:

    This email address is being protected from spambots. You need JavaScript enabled to view it.

Download Area
Certified as

KubeOps GmbH is the owner of the Union trademark KubeOps with the registration number 018305184. 

© KubeOps GmbH. All rights reserved. Subsidiary of