See this folder for Linux and Windows examples on how to use the structure to customize the configuration file. The will be treated as a Go template file, and the config.Node structure is being passed to the template. K3s will generate config.toml for containerd in /var/lib/rancher/k3s/agent/etc/containerd/config.toml.įor advanced customization for this file you can create another file called in the same directory, and it will be used instead. the public and private IPs of the nodes) are included in the NO_PROXY list, or that the nodes can be reached through the proxy.ĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESģe4d34729602 897ce3c5fc8f "entry" About a minute ago Up About a minute k8s_lb-port-443_svclb-traefik-jbmvl_kube-system_d46f10c6-073f-4c7e-8d7a-8e7ac18f9cb0_0īffdc9d7a65f rancher/klipper-lb "entry" About a minute ago Up About a minute k8s_lb-port-80_svclb-traefik-jbmvl_kube-system_d46f10c6-073f-4c7e-8d7a-8e7ac18f9cb0_0Ĥ36b85c5e38d rancher/library-traefik "/traefik -configfi…" About a minute ago Up About a minute k8s_traefik_traefik-758cd5fc85-2wz97_kube-system_07abe831-ffd6-4206-bfa1-7c9ca4fb39e7_0ĭe8fded06188 rancher/pause:3.1 "/pause" About a minute ago Up About a minute k8s_POD_svclb-traefik-jbmvl_kube-system_d46f10c6-073f-4c7e-8d7a-8e7ac18f9cb0_0ħc6a30aeeb2f rancher/pause:3.1 "/pause" About a minute ago Up About a minute k8s_POD_traefik-758cd5fc85-2wz97_kube-system_07abe831-ffd6-4206-bfa1-7c9ca4fb39e7_0Īe6c58cab4a7 9d12f9848b99 "local-path-provisio…" About a minute ago Up About a minute k8s_local-path-provisioner_local-path-provisioner-6d59f47c7-lncxn_kube-system_2dbd22bf-6ad9-4bea-a73d-620c90a6c1c1_0īe1450e1a11e 9dd718864ce6 "/metrics-server" About a minute ago Up About a minute k8s_metrics-server_metrics-server-7566d596c8-9tnck_kube-system_031e74b5-e9ef-47ef-a88d-fbf3f726cbc6_0Ĥ454d14e4d3f c4d3d16fe508 "/coredns -conf /etc…" About a minute ago Up About a minute k8s_coredns_coredns-8655855d6-rtbnb_kube-system_d05725df-4fb1-410a-8e82-2b1c8278a6a1_0Ĭ3675b87f96c rancher/pause:3.1 "/pause" About a minute ago Up About a minute k8s_POD_coredns-8655855d6-rtbnb_kube-system_d05725df-4fb1-410a-8e82-2b1c8278a6a1_0Ĥb1fddbe6ca6 rancher/pause:3.1 "/pause" About a minute ago Up About a minute k8s_POD_local-path-provisioner-6d59f47c7-lncxn_kube-system_2dbd22bf-6ad9-4bea-a73d-620c90a6c1c1_0 You should ensure that the IP address ranges used by the Kubernetes nodes themselves (i.e. K3s will automatically add the cluster internal Pod and Service IP ranges and cluster DNS domain to the list of NO_PROXY entries.
Of course, you can also configure the proxy by editing these files. The K3s installation script will automatically take the HTTP_PROXY, HTTPS_PROXY and NO_PROXY, as well as the CONTAINERD_HTTP_PROXY, CONTAINERD_HTTPS_PROXY and CONTAINERD_NO_PROXY variables from the current shell, if they are present, and write them to the environment file of your systemd service, usually: These proxy settings will then be used in K3s and passed down to the embedded containerd and kubelet. If you are running K3s in an environment, which only has external connectivity through an HTTP proxy, you can configure your proxy settings on the K3s systemd service. It is possible to enable a second static token that can only be used to join agents, or to create temporary kubeadm style join tokens that expire automatically.įor more information, see the k3s token command documentation. This token cannot be changed once the cluster has been created. Token Management īy default, K3s uses a single static token for both servers and agents. Any certificates that are expired, or within 90 days of expiring, are automatically renewed every time K3s starts.įor information on manually rotating client and server certificates, see the k3s certificate rotate command documentation. K3s client and server certificates are valid for 365 days from their date of issuance. These CA certificates are valid for 10 years, and are not automatically renewed.įor information on using custom CA certificates, or renewing the self-signed CA certificates, see the k3s certificate rotate-ca command documentation.
K3s generates self-signed Certificate Authority (CA) Certificates during startup of the first server node. Certificate Management Certificate Authority Certificates This section contains advanced information describing the different ways you can run and manage K3s, as well as steps necessary to prepare the host OS for K3s use.
0 kommentar(er)
