如何在轻量级K3中访问api控制器配置 [英] How do I access api controller config in lightweight K3s

问题描述

通常在常规Kubernetes中的/etc/kubernetes/manifests/kube-apiserver.yaml中找到.

Normally found in /etc/kubernetes/manifests/kube-apiserver.yaml in regular Kubernetes .

在牧场主/K3s中，这就是我所能找到的全部.我正在尝试调整一些设置，以便可以启用自定义自动缩放(例如

In rancher / K3s , this is all I can find. I'm trying to tweak some settings so I can enable custom autoscaling (eg https://docs.bitnami.com/kubernetes/how-to/configure-autoscaling-custom-metrics/ ) . Is there another way I can affect these settings?

$ sudo tree /var/lib/rancher/k3s/server/manifests
/var/lib/rancher/k3s/server/manifests
├── coredns.yaml
├── rolebindings.yaml
└── traefik.yaml

0 directories, 3 files

推荐答案

K3s捆绑了Kubernetes组件(kube-apiserver，kube-controller-manager，kube-scheduler，kubelet，kube-proxy)进入作为简单服务器和代理呈现的组合过程模型.运行k3s服务器将启动Kubernetes服务器并自动将本地主机注册为代理.k3s支持多节点模型，用户可以使用流程启动.默认情况下，k3s同时安装服务器和代理(结合了Kubelet，kubeproxy和法兰绒代理流程)，可以使用-disable-agent"来控制相同的内容，其中服务器和代理(Kubernetes术语中的主节点和节点)可以分开.

K3s bundles the Kubernetes components (kube-apiserver, kube-controller-manager, kube-scheduler, kubelet, kube-proxy) into combined processes that are presented as a simple server and agent model. Running k3s server will start the Kubernetes server and automatically register the local host as an agent. k3s supports multi-node model where users can use the ‘node-token’ generated while the process startup. By default k3s installs both server and agent (combined the Kubelet, kubeproxy and flannel agent processes), the same can be controlled using ‘ — disable-agent’ where server and agent (master and node in Kubernetes terminology) can be separated.

据我所见-k3的所有配置文件都可以在/var/lib/rancher/k3s 目录下找到:

As per I see - all configuration files for k3s can be fount under /var/lib/rancher/k3s directory:

Running kube-apiserver --advertise-port=6443 --allow-privileged=true 
--api-audiences=unknown --authorization-mode=Node,RBAC --basic-auth-file=/var/lib/ranch
er/k3s/server/cred/passwd 
--bind-address=127.0.0.1 --cert-dir=/var/lib/rancher/k3s/server/tls/temporary-certs --client-ca-file=/var/lib/rancher/k3s/server/tls/client-ca.crt 
--enable-admission-p
lugins=NodeRestriction --insecure-port=0 
--kubelet-client-certificate=/var/lib/rancher/k3s/server/tls/client-kube-apiserver.crt 
--kubelet-client-key=/var/lib/rancher/k3s/server/tls/client-kube-
apiserver.key 
--proxy-client-cert-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.crt
 --proxy-client-key-file=/var/lib/rancher/k3s/server/tls/client-auth-proxy.key --requestheader-allowe
d-names=system:auth-proxy 
--requestheader-client-ca-file=/var/lib/rancher/k3s/server/tls/request-header-ca.crt 
--requestheader-extra-headers-prefix=X-Remote-Extra- 
--requestheader-group-headers
=X-Remote-Group --requestheader-username-headers=X-Remote-User
 --secure-port=6444 --service-account-issuer=k3s --service-account-key-file=/var/lib/rancher/k3s/server/tls/service.key 
--service-a
ccount-signing-key-file=/var/lib/rancher/k3s/server/tls/service.key 
--service-cluster-ip-range=10.43.0.0/16 --tls-cert-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.crt --tls-priv
ate-key-file=/var/lib/rancher/k3s/server/tls/serving-kube-apiserver.key

您还可以使用-kube-apiserver-arg 查看全文