티스토리 뷰

Cloud/Kubernetes

K3s

jacobbaek Jacob_baek 2019. 11. 17. 23:27

K3s 란

가벼운 Kubernetes로 쉽게 설치하고 적은 메모리/binary 파일을 사용하여 Edge/IoT 환경 혹은 CI/Dev 환경에서 k8s를 쉽게 사용할 수 있도록 도와주는 도구이다.

installation

K3s 설치

설치는 간단하다. 아래와 같이 shell script를 제공하며 바로 다운받아 설치를 진행한다.

[root@deploy ~]# curl -sfL https://get.k3s.io | sh -
[INFO]  Finding release for channel stable
[INFO]  Using v1.20.2+k3s1 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.20.2+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/rancher/k3s/releases/download/v1.20.2+k3s1/k3s
...

설치후에 아래와 같은 경로에 kubeconfig 파일에 해당되는 yaml파일이 존재하게 된다.

[root@deploy ~]# cat /etc/rancher/k3s/k3s.yaml
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJkakNDQVIyZ0F3SUJBZ0lCQURBS0JnZ3Foa2pPUFFRREFqQWpNU0V3SHdZRFZRUUREQmhyTTNNdGMyVnkKZG1WeUxXTmhRREUyTVRJM05qRTFPRFF3SGhjTk1qRXdNakE0TURVeE9UUTBXaGNOTXpFd01qQTJNRFV4T1RRMApXakFqTVNFd0h3WURWUVFEREJock0zTXRjMlZ5ZG1WeUxXTmhRREUyTVRJM05qRTFPRFF3V1RBVEJnY3Foa2pPClBRSUJCZ2dxaGtqT1BRTUJCd05DQUFSNFN0UHo0emJmenE3NXUvMjc5TDZ6NjJmemZETUdVN3FGMS8ybnB6OWMKZWxsYzdpNVB0d21BMDRlQ0VtTUZqalJaNHE3NGh5RGJsZ3I1cmpqaVNwKzJvMEl3UURBT0JnTlZIUThCQWY4RQpCQU1DQXFRd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBZEJnTlZIUTRFRmdRVXlFL3FHbndQVFNwVm9hYlQvaW9MCjdwVU5LZVF3Q2dZSUtvWkl6ajBFQXdJRFJ3QXdSQUlnQ1hUTStRVWlwSGVOODdxN2xKRHRLWVdkWWFFeDRwblMKQk44ajZGTWx6RVVDSURmZXpGRDF4aHZzaVora0Y2YVNmNm5vZG8zNVlFdDN5a1NnVGY4bXZLOFUKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
    server: https://127.0.0.1:6443
    ...

다음과 같이 VERSION과 kubeconfig MODE를 지정해서 원하는 환경과 kubeconfig 사용시 operation not permitted 이슈를 사전에 방지해놓는다.

jacob@jacob-laptop:~$ curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.19.7+k3s1 K3S_KUBECONFIG_MODE="644" sh -s -
[INFO]  Using v1.19.7+k3s1 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.19.7+k3s1/sha256sum-amd64.txt
[INFO]  Downloading binary https://github.com/rancher/k3s/releases/download/v1.19.7+k3s1/k3s
[INFO]  Verifying binary download
[INFO]  Installing k3s to /usr/local/bin/k3s
[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, command exists in PATH at /snap/bin/kubectl
...

k3s는 daemon 형태로 동작되며

[root@jacob-deploy ~]#  systemctl status k3s
● k3s.service - Lightweight Kubernetes
   Loaded: loaded (/etc/systemd/system/k3s.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2021-02-08 09:48:45 KST; 30min ago
     Docs: https://k3s.io
  Process: 1470 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
  Process: 1468 ExecStartPre=/sbin/modprobe br_netfilter (code=exited, status=0/SUCCESS)
 Main PID: 1473 (k3s-server)
    Tasks: 167
   Memory: 735.6M
   CGroup: /system.slice/k3s.service
           ├─1473 /usr/local/bin/k3s server
           ├─1502 containerd
           ├─1953 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─1965 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2174 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2853 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2899 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2927 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2961 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2975 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           ├─2989 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...
           └─3129 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/cont...

Feb 08 10:17:11 jacob-deploy k3s[1473]: E0208 10:17:11.529073    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:17:42 jacob-deploy k3s[1473]: E0208 10:17:42.183386    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:17:42 jacob-deploy k3s[1473]: E0208 10:17:42.184526    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:18:12 jacob-deploy k3s[1473]: E0208 10:18:12.834310    1473 sample_and_watermark.go:200] Time went bac...igh"}
Feb 08 10:18:12 jacob-deploy k3s[1473]: E0208 10:18:12.836101    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:18:12 jacob-deploy k3s[1473]: E0208 10:18:12.836493    1473 sample_and_watermark.go:200] Time went bac...igh"}
Feb 08 10:18:12 jacob-deploy k3s[1473]: E0208 10:18:12.836890    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:18:12 jacob-deploy k3s[1473]: E0208 10:18:12.837370    1473 sample_and_watermark.go:200] Time went bac...nly"}
Feb 08 10:18:43 jacob-deploy k3s[1473]: E0208 10:18:43.492053    1473 sample_and_watermark.go:200] Time went bac...igh"}
Feb 08 10:18:43 jacob-deploy k3s[1473]: E0208 10:18:43.492692    1473 sample_and_watermark.go:200] Time went bac...igh"}
Hint: Some lines were ellipsized, use -l to show in full.

실제 동작되는 k3s process는 다음과 같다.

[root@jacob-deploy ~]# ps -ef | grep k3s
root      1473     1 11 09:48 ?        00:03:23 /usr/local/bin/k3s server
root      1953     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 7a4df6840b499f5cad5104299569277593fafb418d5d08c299b43273434a5bf1 -address /run/k3s/containerd/containerd.sock
root      1965     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id aab1841a0cf579b471d14f2dd8ff95deb7fb92e49e54154d012b46f7aa96def7 -address /run/k3s/containerd/containerd.sock
root      2174     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 6421b6948dc2cb601c2ee2107713e84044acd3cb6a56fa7786050511c2dbc029 -address /run/k3s/containerd/containerd.sock
root      2853     1 21 09:48 ?        00:06:17 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 5d3e60aaf3b996784e21ecefa684eee14e37e6e584f4335f609d4b53ed518186 -address /run/k3s/containerd/containerd.sock
root      2899     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 42808a68a20ad393734b20e69c4eb4271685e03a4690f655068581623c81dd79 -address /run/k3s/containerd/containerd.sock
root      2927     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 54344b06545c9929527fc29ff6d0bcd3e4424aaf776f5472b8f35ce70590dfd6 -address /run/k3s/containerd/containerd.sock
root      2961     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 36daee693c2eb2f53bef6d52b13e0c4f079dd69211cc33c06cf4b76421f01c94 -address /run/k3s/containerd/containerd.sock
root      2975     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id e70dff7ce8881047fca25bef1ce1d28b81bebd5ac90e505d9abf801ba8105cda -address /run/k3s/containerd/containerd.sock
root      2989     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id ee0098d9fb799b29f13dc4d64e19c4169ee0f6a72ba9a393b0bee65d196f763b -address /run/k3s/containerd/containerd.sock
root      3129     1  0 09:48 ?        00:00:00 /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin/containerd-shim-runc-v2 -namespace k8s.io -id 0bbf90678bdd219d3318574c7c1e11227347a352831b5372bb19

아래와 같이 변수를 추가하여 설치를 custom 하게 수행할 수 있다.

[root@deploy ~]# curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.19.7+k3s1 K3S_KUBECONFIG_MODE="644" INSTALL_K3S_EXEC="--no-deploy traefik" sh -s -

실제 환경변수들을 https://get.k3s.io 다운로드시 파일로 다운로드 받아보면 확인할 수 있다.
대표적인 환경변수들은 아래에서 확인가능하다.

node 추가

만약 worker node를 추가하고자 한다면 아래 명령과 같이 master로 동작될 node의 token을 확인하고 worker로 동작될 node에 해당 token을 이용해 설치를 진행하면 된다.

[root@deploy ~]# cat /var/lib/rancher/k3s/server/node-token
K1086931532f8555e790c7ba8962eeaf4ee1a38e5f5855cd081601060c12f0e9015::server:7f9d963be595cda2a96914ff58d8a3d1
...
[root@node1 ~]# curl -sfL https://get.k3s.io | K3S_URL=https://192.168.56.5:6443 K3S_TOKEN=K1086931532f8555e790c7ba8962eeaf4ee1a38e5f5855cd081601060c12f0e9015::server:7f9d963be595cda2a96914ff58d8a3d1 sh -

만약 기존 k3s설치시 버전을 지정했다면 버전을 맞추기 위해 node 추가 과정에서도 추가해주도록 한다.

curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=v1.19.7+k3s1 K3S_URL=https://192.168.1.1:6443 K3S_TOKEN=xxxxxxxxx sh -

실제 배포가 된뒤 node를 확인하면 추가된 node가 확인된다.

root@node1:~# kubectl get nodes
NAME       STATUS   ROLES    AGE     VERSION
node1   Ready    master   22h     v1.19.7+k3s1
node2   Ready    <none>   4m36s   v1.19.7+k3s1

설정 확인 및 기타 명령들

k3s 설정확인은 다음과 같은 명령을 통해서 해볼수 있다.

root@localhost:~# k3s check-config

Verifying binaries in /var/lib/rancher/k3s/data/8f4b194129852507eab4a55117fc942e0688ec9a70ffdaa5911ccc6652220f76/bin:
- sha256sum: good
- links: good

System:
- /usr/sbin iptables v1.8.4 (legacy): ok
- swap: disabled
- routes: default CIDRs 10.42.0.0/16 or 10.43.0.0/16 already routed

Limits:
- /proc/sys/kernel/keys/root_maxkeys: 1000000

modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-62-generic
info: reading kernel config from /boot/config-5.4.0-62-generic ...

Generally Necessary:
- cgroup hierarchy: properly mounted [/sys/fs/cgroup]
- /usr/sbin/apparmor_parser
apparmor: enabled and tools installed
- CONFIG_NAMESPACES: enabled
- CONFIG_NET_NS: enabled
- CONFIG_PID_NS: enabled
- CONFIG_IPC_NS: enabled
- CONFIG_UTS_NS: enabled
- CONFIG_CGROUPS: enabled
- CONFIG_CGROUP_CPUACCT: enabled
- CONFIG_CGROUP_DEVICE: enabled
- CONFIG_CGROUP_FREEZER: enabled
- CONFIG_CGROUP_SCHED: enabled
- CONFIG_CPUSETS: enabled
- CONFIG_MEMCG: enabled
- CONFIG_KEYS: enabled
- CONFIG_VETH: enabled (as module)
- CONFIG_BRIDGE: enabled (as module)
- CONFIG_BRIDGE_NETFILTER: enabled (as module)
- CONFIG_IP_NF_FILTER: enabled (as module)
- CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
- CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module)
- CONFIG_IP_NF_NAT: enabled (as module)
- CONFIG_NF_NAT: enabled (as module)
- CONFIG_POSIX_MQUEUE: enabled

Optional Features:
- CONFIG_USER_NS: enabled
- CONFIG_SECCOMP: enabled
- CONFIG_CGROUP_PIDS: enabled
- CONFIG_BLK_CGROUP: enabled
- CONFIG_BLK_DEV_THROTTLING: enabled
- CONFIG_CGROUP_PERF: enabled
- CONFIG_CGROUP_HUGETLB: enabled
- CONFIG_NET_CLS_CGROUP: enabled (as module)
- CONFIG_CGROUP_NET_PRIO: enabled
- CONFIG_CFS_BANDWIDTH: enabled
- CONFIG_FAIR_GROUP_SCHED: enabled
- CONFIG_RT_GROUP_SCHED: missing
- CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module)
- CONFIG_IP_SET: enabled (as module)
- CONFIG_IP_VS: enabled (as module)
- CONFIG_IP_VS_NFCT: enabled
- CONFIG_IP_VS_PROTO_TCP: enabled
- CONFIG_IP_VS_PROTO_UDP: enabled
- CONFIG_IP_VS_RR: enabled (as module)
- CONFIG_EXT4_FS: enabled
- CONFIG_EXT4_FS_POSIX_ACL: enabled
- CONFIG_EXT4_FS_SECURITY: enabled
- Network Drivers:
  - "overlay":
    - CONFIG_VXLAN: enabled (as module)
      Optional (for encrypted networks):
      - CONFIG_CRYPTO: enabled
      - CONFIG_CRYPTO_AEAD: enabled
      - CONFIG_CRYPTO_GCM: enabled
      - CONFIG_CRYPTO_SEQIV: enabled
      - CONFIG_CRYPTO_GHASH: enabled
      - CONFIG_XFRM: enabled
      - CONFIG_XFRM_USER: enabled (as module)
      - CONFIG_XFRM_ALGO: enabled (as module)
      - CONFIG_INET_ESP: enabled (as module)
      - CONFIG_INET_XFRM_MODE_TRANSPORT: missing
- Storage Drivers:
  - "overlay":
    - CONFIG_OVERLAY_FS: enabled (as module)

STATUS: pass

아래와 같이 /etc/rancher/k3s/ 디렉토리내에 kubeconfig 파일을 확인할 수 있다.

root@localhost:~# kubectl --kubeconfig /etc/rancher/k3s/k3s.yaml get nodes
NAME       STATUS   ROLES                  AGE   VERSION
service1   Ready    control-plane,master   11h   v1.20.2+k3s1

별도의 옵션 없이 kubectl을 사용하고자 한다면 아래와 같이 복사를 하여 사용하자.

root@localhost:~# cp /etc/rancher/k3s/k3s.yaml ~/.kube/config
root@localhost:~# kubectl get po
No resources found in default namespace.

별도의 옵션 없이 script을 통한 k3s install을 하게 되면 ingress 용도의 Treafik이 설치된다.

실제 container 들을 확인해보고 싶다면 default runtime인 containerd를 통해 확인해볼수 있다.

root@deploy:~# ctr containers list
CONTAINER                                                           IMAGE                                                                      RUNTIME
08d273eee9dd93379fd6b7f84d2911bcbd8d521a3cd34ddf8a3c60b4b651755a    docker.io/rancher/klipper-lb:v0.1.2                                        io.containerd.runc.v2
0ecc6631cb565b0de3176eb4dce87de7cc0cd81ff94f7234f6305eefe8e58caa    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
13799fd9747bca4abc85d50e462feda66f71f0b43afdbf46ac9361d9ffea7e5b    docker.io/longhornio/longhorn-instance-manager:v1_20201216                 io.containerd.runc.v2
2c7ab3466c5c5e75fa170e06828e386095b90572697347f81313f783b2b189e6    docker.io/longhornio/longhorn-manager:v1.1.0                               io.containerd.runc.v2
3b074f38000848d9bf85411c61bf18f64c86e29a8de9f78b0ddce566b215880a    sha256:9533374f65a25ecf6bf99daccf5e40431445a1fb9be3ac14a9bbdc5f638db361    io.containerd.runc.v2
416c17990970ed8742b1107b0ba16a1e84f9565b4f3085c9dd9368bb5d592f12    docker.io/longhornio/longhorn-manager:v1.1.0                               io.containerd.runc.v2
61cb0e0adce7cb8351f7be08485c72e6b7755b7d835743483f073a2112974186    sha256:3a555222b6ae444f7a6a1bd73c1da0b4cd5bf942335ac1da76a88469ab0fe3eb    io.containerd.runc.v2
81f9906e9d7afaffd5a1c9ee5664f2f2a59c1fb5091379d9192b6b6ba9e8c7dc    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
9403867bbc6450cc4e1bb87e410f41a5e67bb1719417e4e0e974698c94aa4dab    docker.io/longhornio/longhorn-engine:v1.1.0                                io.containerd.runc.v2
b6def6a2e1a5f06b0e247ac03d33480529d4434778ef00711b17b1d3e168ec34    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
d0855797a7a57b315ad4fa25fb72c9dedb9f695c0cf7bf56719b4ec91fe7cf8a    docker.io/longhornio/longhorn-instance-manager:v1_20201216                 io.containerd.runc.v2
d0ecab883e4972ade3fa28c65014e88e17d337e88274966c322039299a9f0c3c    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
f2efaba550d9378dfc7924bdba797c0a2144546a3dd40ccb78f0f23d884ad1b1    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
fa55f117f8a7472bfef940dc2ff112d8222d3a702f5ad934fec55be5c218a41f    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2
fde91929f839a454f3da77b97e60d9eff5875e1436b5be484429d978179d51db    docker.io/rancher/pause:3.1                                                io.containerd.runc.v2

참고로 K3d라는 Project도 있으며 이는 다수의 K3s를 docker 기반으로 빠르게 환경을 구성해주는 도구이다.
즉, containerized k3s cluster를 구성해준다. 운영보다는 로컬 기반의 개발/테스트용도로 보인다.

기본 구성

storage class

기본적으로 local path provisioner로 volume 생성을 할수 있도록 기본 설치된다.

root@deploy:~# kubectl get sc
NAME                   PROVISIONER             RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
local-path (default)   rancher.io/local-path   Delete          WaitForFirstConsumer   false                  16h

다음 명령을 통해 생성을 확인해볼수 있다.
(아래 예제는 pvc만 생성하면 pending 상태로 대기하게 된다. pod까지 생성해야 volume생성을 확인할 수 있다. 경로는 default 경로인 /var/lib/rancher/k3s/storage 이다.)

kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pvc/pvc.yaml
kubectl create -f https://raw.githubusercontent.com/rancher/local-path-provisioner/master/examples/pod/pod.yaml

참고로 Longhorn으로도 동작이 잘된다.

ingress

기본으로 treafik이 설치되도록 되어 있다.
설치 과정중에 treafik을 제외시킬수도 있고 설치후 helm을 이용해 삭제할 수도 있다.

CNI

flannel이 기본 설치된다.

아래 네트워크 정보와 같이 flannel interface를 확인할 수 있다.

root@service1:~# ip link | more -10
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:3e:82:a7 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 52:54:00:ca:af:94 brd ff:ff:ff:ff:ff:ff
4: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN mode DEFAULT group default
    link/ether 0a:d7:66:12:91:63 brd ff:ff:ff:ff:ff:ff
5: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 62:99:42:14:0e:7f brd ff:ff:ff:ff:ff:ff

그외 명령들

[root@deploy ~]# which k3s-uninstall.sh
/usr/local/bin/k3s-uninstall.sh
[root@deploy ~]# which k3s-killall.sh
/usr/local/bin/k3s-killall.sh

K3s on Baremetal

참고사이트

'Cloud > Kubernetes' 카테고리의 다른 글

ingress with subpath  (0) 2021.03.23
Cluster-API  (0) 2021.03.20
kubernetes ingress  (0) 2021.03.15
Longhorn  (0) 2021.03.13
K3s with calico  (0) 2021.03.05
K3s  (0) 2019.11.17
댓글
댓글쓰기 폼