The replacement is called cri-dockerd # and should be enabled if you want to keep using Docker as your # container runtime # Only available to enable in Kubernetes 1.21 and higher enable_cri_dockerd: true # Cluster level SSH private key # Used if no ssh information is set for the node ssh_key_path: ~/.ssh/test # Enable use of SSH agent to use SSH private keys with passphrase # This requires the environment `SSH_AUTH_SOCK` configured pointing #to your SSH agent which has the private key added ssh_agent_auth: true # List of registry credentials # If you are using a Docker Hub registry, you can omit the `url` # or set it to `docker.io` # is_default set to `true` will override the system default # registry set in the global settings private_registries: - url: user: Username password: password is_default: true # Bastion/Jump host configuration bastion_host: address: x.x.x.x user: ubuntu port: 22 ssh_key_path: /home/user/.ssh/bastion_rsa # or # ssh_key: |- # -BEGIN RSA PRIVATE KEY- # -END RSA PRIVATE KEY- # Set the name of the Kubernetes cluster cluster_name: mycluster # The Kubernetes version used. 1.6 labels: app: ingress taints: - key: test-key value: test-value effect: NoSchedule # If set to true, RKE will not fail when unsupported Docker version # are found ignore_docker_version: false # Enable running cri-dockerd # Up to Kubernetes 1.23, kubelet contained code called dockershim # to support Docker runtime. address: user: ubuntu role: - worker hostname_override: node3 internal_address: 192.168. Ssh_cert_path: /home/user/.ssh/test-key-cert.pub ssh_cert: | AAAAHHNzaC1yc2EtY2VydC12MDFAb3Bl. BEGIN RSA PRIVATE KEY-END RSA PRIVATE KEY.

2.2 user: ubuntu role: - worker ssh_key_path: /home/user/.ssh/id_rsa ssh_key: |. 1.1 user: ubuntu role: - controlplane - etcd port: 2222 docker_socket: /var/run/docker.sock - address: 2.2.

Maxx claster vst