So if you uncheck the following box (unclear from the docs what command it uses): dns-port=10053 -config-dir=/kube-dns-config -v=2Ĥ190 root 0:05 /usr/local/bin/kube-proxy -config=/var/lib/kube-proxy/nfĤ216 65534 0:03 /sidecar -v=2 -logtostderr -probe=kubedns,127.0.0.1:10053.local,5,SRV -probe=dnsmasq,127.0.0.1:53.local,5,SRVĤ606 root 0:00 /compose-controller -kubeconfig -reconciliation-interval 30sĤ905 root 0:01 /api-server -kubeconfig -authentication-kubeconfig -authorization-kubeconfig -etcd-servers= -etcd-cafile=/etc/docker-compose/etcd/ca.crt -etcd-certfile=/etc/docker-compose/etcd/client.crt -etcd-keyfile=/etc/docker-compose/etcd/client.key -secure-port=9443 -tls-ca-file=/etc/docker-compose/tls/ca.crt -tls-cert-file=/etc/docker-compose/tls/server.crt -tls-private-key-file=/etc/docker-compose/tls/server.key Then you can see all the Kubernetes processes in the VM: linuxkit-025000000001:~# ps -Af | grep kubeġ251 root 0:00 /usr/bin/logwrite -n kubelet /usr/bin/kubelet.shġ288 root 0:51 kubelet -kubeconfig=/etc/kubernetes/nf -bootstrap-kubeconfig=/etc/kubernetes/nf -pod-manifest-path=/etc/kubernetes/manifests -allow-privileged=true -cluster-dns=10.96.0.10 -cluster-domain=cluster.local -cgroups-per-qos=false -enforce-node-allocatable= -network-plugin=cni -cni-conf-dir=/etc/cni/net.d -cni-bin-dir=/opt/cni/bin -cadvisor-port=0 -kube-reserved-cgroup=podruntime -system-reserved-cgroup=systemreserved -cgroup-root=kubepods -hostname-override=docker-for-desktop -fail-swap-on=falseģ564 root 0:26 kube-scheduler -address=127.0.0.1 -leader-elect=true -kubeconfig=/etc/kubernetes/nfģ616 root 1:45 kube-controller-manager -cluster-signing-key-file=/run/config/pki/ca.key -address=127.0.0.1 -root-ca-file=/run/config/pki/ca.crt -service-account-private-key-file=/run/config/pki/sa.key -kubeconfig=/etc/kubernetes/nf -cluster-signing-cert-file=/run/config/pki/ca.crt -leader-elect=true -use-service-account-credentials=true -controllers=*,bootstrapsigner,tokencleanerģ644 root 1:59 kube-apiserver -admission-control=Initializers,NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,DefaultTolerationSeconds,NodeRestriction,MutatingAdmissionWebhook,ValidatingAdmissionWebhook,ResourceQuota -requestheader-username-headers=X-Remote-User -requestheader-group-headers=X-Remote-Group -service-account-key-file=/run/config/pki/sa.pub -secure-port=6443 -insecure-port=8080 -insecure-bind-address=0.0.0.0 -requestheader-client-ca-file=/run/config/pki/front-proxy-ca.crt -kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname -requestheader-extra-headers-prefix=X-Remote-Extra-advertise-address=192.168.65.3 -service-cluster-ip-range=10.96.0.0/12 -tls-private-key-file=/run/config/pki/apiserver.key -enable-bootstrap-token-auth=true -requestheader-allowed-names=front-proxy-client -tls-cert-file=/run/config/pki/apiserver.crt -proxy-client-key-file=/run/config/pki/front-proxy-client.key -proxy-client-cert-file=/run/config/pki/front-proxy-client.crt -allow-privileged=true -client-ca-file=/run/config/pki/ca.crt -kubelet-client-certificate=/run/config/pki/apiserver-kubelet-client.crt -kubelet-client-key=/run/config/pki/apiserver-kubelet-client.key -authorization-mode=Node,RBAC -etcd-servers= -etcd-cafile=/run/config/pki/etcd/ca.crt -etcd-certfile=/run/config/pki/apiserver-etcd-client.crt -etcd-keyfile=/run/config/pki/apiserver-etcd-client.keyģ966 root 0:01 /kube-dns -domain=cluster.local.
You can connect to the VM with this: screen ~/Library/Containers//Data/vms/0/tty
Kubernetes runs in the same Hyperkit VM created for docker and the kube-apiserver is exposed.
Manually install kubernetes cluster on mac for mac#
Docker for Mac uses these components: Hyperkit, VPNkit and DataKit
0 kommentar(er)
