Merge 62b80237ef into f50d335451

roles/download/meta/main.yml

@@ -1,8 +0,0 @@
----
-argument_specs:
-  main:
-    short_description: Manage the downloading of K3S binaries
-    options:
-      k3s_version:
-        description: The desired version of K3S
-        required: true

roles/k3s_agent/defaults/main.yml

@@ -1,5 +1,2 @@
 ---
-is_pxe_booted: false
-extra_agent_args: ""
-group_name_master: master
 systemd_dir: /etc/systemd/system

roles/k3s_agent/meta/main.yml

@@ -1,29 +0,0 @@
----
-argument_specs:
-  main:
-    short_description: Setup k3s agents
-    options:
-      apiserver_endpoint:
-        description: Virtual ip-address configured on each master
-        required: true
-
-      extra_agent_args:
-        description: Virtual ip-address configured on each master
-        default: Arguments passed to the systemd service
-
-      group_name_master:
-        description: Name of the master group
-        default: master
-
-      proxy_env:
-        type: dict
-        description: Internet proxy configurations
-        default: ~
-        options:
-          HTTP_PROXY:
-          HTTPS_PROXY:
-          NO_PROXY:
-
-      systemd_dir:
-        description: Path to systemd services
-        default: /etc/systemd/system

roles/k3s_custom_registries/meta/main.yml

@@ -1,19 +0,0 @@
----
-argument_specs:
-  main:
-    short_description: Configure the use of a custom container registry
-    options:
-      custom_registries_yaml:
-        description:
-          - YAML block defining custom registries.
-          - >
-            The following is an example that pulls all images used in
-            this playbook through your private registries.
-          - >
-            It also allows you to pull your own images from your private
-            registry, without having to use imagePullSecrets in your
-            deployments.
-          - >
-            If all you need is your own images and you don't care about
-            caching the docker/quay/ghcr.io images, you can just remove
-            those from the mirrors: section.

roles/k3s_server/defaults/main.yml

@@ -2,9 +2,9 @@
 # If you want to explicitly define an interface that ALL control nodes
 # should use to propagate the VIP, define it here. Otherwise, kube-vip
 # will determine the right interface automatically at runtime.
-kube_vip_iface: ~
+kube_vip_iface: null
 
-kube_vip_cloud_provider_tag_version: main
+# Name of the master group
 group_name_master: master
 
 # yamllint disable rule:line-length

roles/k3s_server/meta/main.yml

@@ -1,25 +0,0 @@
----
-argument_specs:
-  main:
-    short_description: Setup k3s servers
-    options:
-      group_name_master:
-        description: Name of the master group
-        default: master
-
-      kube_vip_cloud_provider_tag_version:
-        description: Tag for kube-vip-cloud-provider manifest when enabled
-        default: main
-
-      kube_vip_lb_ip_range:
-        description: IP range for kube-vip load balancer
-        default: ~
-
-      proxy_env:
-        type: dict
-        description: Internet proxy configurations
-        default: ~
-        options:
-          HTTP_PROXY:
-          HTTPS_PROXY:
-          NO_PROXY: