diff --git a/roles/download/meta/main.yml b/roles/download/meta/main.yml new file mode 100644 index 0000000..e7911d5 --- /dev/null +++ b/roles/download/meta/main.yml @@ -0,0 +1,8 @@ +--- +argument_specs: + main: + short_description: Manage the downloading of K3S binaries + options: + k3s_version: + description: The desired version of K3S + required: true diff --git a/roles/k3s_agent/defaults/main.yml b/roles/k3s_agent/defaults/main.yml index 0b45925..037c1f3 100644 --- a/roles/k3s_agent/defaults/main.yml +++ b/roles/k3s_agent/defaults/main.yml @@ -1,2 +1,5 @@ --- +is_pxe_booted: false +extra_agent_args: "" +group_name_master: master systemd_dir: /etc/systemd/system diff --git a/roles/k3s_agent/meta/main.yml b/roles/k3s_agent/meta/main.yml new file mode 100644 index 0000000..a2f694c --- /dev/null +++ b/roles/k3s_agent/meta/main.yml @@ -0,0 +1,29 @@ +--- +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 diff --git a/roles/k3s_custom_registries/meta/main.yml b/roles/k3s_custom_registries/meta/main.yml new file mode 100644 index 0000000..0ec0e7c --- /dev/null +++ b/roles/k3s_custom_registries/meta/main.yml @@ -0,0 +1,19 @@ +--- +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. diff --git a/roles/k3s_server/defaults/main.yml b/roles/k3s_server/defaults/main.yml index 1ab5b83..f088c96 100644 --- a/roles/k3s_server/defaults/main.yml +++ b/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: null +kube_vip_iface: ~ -# Name of the master group +kube_vip_cloud_provider_tag_version: main group_name_master: master # yamllint disable rule:line-length diff --git a/roles/k3s_server/meta/main.yml b/roles/k3s_server/meta/main.yml new file mode 100644 index 0000000..cbe37ea --- /dev/null +++ b/roles/k3s_server/meta/main.yml @@ -0,0 +1,25 @@ +--- +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: