https://docs.daper.io/flatcar/index.htmlRecent content in Flatcar Linux on DocumentationHugo -- gohugo.ioen-ushttps://docs.daper.io/flatcar/crio/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://docs.daper.io/flatcar/crio/index.htmlcri-o crun Install CRUN Download the latest release and put it on /opt/bin. wget -O /opt/bin/crun https://github.com/containers/crun/releases/download/1.6/crun-1.6-linux-amd64 Install CRI-O Download the latest release and untar it. Use the install script with the following configuration: export BINDIR=/opt/bin export SYSTEMDDIR=/etc/systemd/system export OCIDIR=/etc export PREFIX=/tmp ./install Then you need to update some files sed -i 's/\/usr\/local\/bin\/crio/\/opt\/bin\/crio/' /etc/systemd/system/crio.service mkdir /etc/systemd/system/crio.service.d /var/lib/crio cat <<EOF > /etc/systemd/system/crio.service.d/10-use-custom-path.conf [Service] Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/opt/bin" EOF cat <<EOF > /etc/containers/registries.conf [registries.search] registries = ['registry.https://docs.daper.io/flatcar/k3s/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://docs.daper.io/flatcar/k3s/index.htmlWrite its configuration file: mkdir -p /etc/rancher/k3s cat <<EOF > /etc/rancher/k3s/config.yaml kube-controller-manager-arg: - "bind-address=0.0.0.0" - "flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins/nodeagent~uds" kube-proxy-arg: - "metrics-bind-address=0.0.0.0" kube-scheduler-arg: - "bind-address=0.0.0.0" kubelet-arg: - "allowed-unsafe-sysctls=net.ipv6.conf.all.disable_ipv6" - "cgroup-driver=systemd" - "volume-plugin-dir=/var/lib/kubelet/volumeplugins" disable: - servicelb - traefik - metrics-server flannel-backend: none etcd-expose-metrics: true node-ip: <node-ip> cluster-cidr: 10.33.0.0/16 service-cidr: 10.34.0.0/16 service-node-port-range: 1-32767 disable-network-policy: true container-runtime-endpoint: unix:///run/crio/crio.sock default-local-storage-path: /var/lib/rancher/k3s/volumes EOF Execute the installation script as root: curl -sfL https://get.k3s.io | sh -https://docs.daper.io/flatcar/calico/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://docs.daper.io/flatcar/calico/index.htmlInstall Tigera operator with: kubectl create -f https://raw.githubusercontent.com/projectcalico/calico/v3.24.1/manifests/tigera-operator.yaml Now create the custom resources cat <<EOF | kubectl create -f- # This section includes base Calico installation configuration. # For more information, see: https://projectcalico.docs.tigera.io/master/reference/installation/api#operator.tigera.io/v1.Installation apiVersion: operator.tigera.io/v1 kind: Installation metadata: name: default spec: # Configures Calico networking. calicoNetwork: # Note: The ipPools section cannot be modified post-install. ipPools: - blockSize: 26 cidr: 10.33.0.0/16 encapsulation: VXLANCrossSubnet natOutgoing: Enabled nodeSelector: all() flexVolumePath: None --- # This section configures the Calico API server.https://docs.daper.io/flatcar/customize-containerd/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://docs.daper.io/flatcar/customize-containerd/index.htmlThe default configuration under /run/torcx/unpack/docker/usr/share/containerd/config.toml can’t be changed but you can copy it to /etc/containerd/config.toml and modify it. Then create a /etc/systemd/system/containerd.service.d/10-use-custom-config.conf unit drop-in file to select the new configuration: [Service] ExecStart= ExecStart=/usr/bin/containerd On a running system, execute systemctl daemon-reload ; systemctl restart containerd for it to take effect. /etc/containerd/config.toml version = 2 # persistent data location root = "/var/lib/containerd" # runtime state information state = "/run/containerd" # set containerd as a subreaper on linux when it is not running as PID 1 subreaper = true # set containerd's OOM score oom_score = -999 disabled_plugins = [] # grpc configuration [grpc] address = "/run/containerd/containerd.https://docs.daper.io/flatcar/kube-vip/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://docs.daper.io/flatcar/kube-vip/index.htmlFirst of all we need to tell the systemd-networkd that kube-vip will manage all interfaces starting with vip-. Create a file named /etc/systemd/network/10-vip.network with the following content: [Match] Name=vip-* [Link] Unmanaged=yes And reload the networkd daemon with networkctl reload. Then we can use the kube-vip binary to generate a manifest to install it on the cluster. Issue this command: kube-vip manifest daemonset \ --arp \ --enableLoadBalancer \ --inCluster \ --serviceInterface eth0 \ --services \ --servicesElection Now generate a config map for its configuration (this will be used by the cloud controller to auto assign 0.