Skip to content

Commit d96eddd

Browse files
committed
updated k3s docs
1 parent 03fe568 commit d96eddd

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

ansible/roles/k3s/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Installs k3s agent and server services on nodes and an ansible-init playbook to
88
Requirements
99
------------
1010

11-
`azimuth_cloud.image_utils.linux_ansible_init` must have been run previously on targeted nodes
11+
`azimuth_cloud.image_utils.linux_ansible_init` must have been run previously on targeted nodes during image build.
1212

1313
Role Variables
1414
--------------

docs/k3s.README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,4 @@ access to the Kubernetes API. The `k3s` role installs Helm for package managemen
55

66
# Idempotency
77
K3s is intended to only be installed during image build as it is configured by the appliance on first boot with `azimuth_cloud.image_utils.linux_ansible_init`. Therefore, the `k3s` role isn't
8-
idempotent and changes to variables will not be reflected in the image when running `site.yml`. An additional consequence of this is that for changes to role variables to be correctly applied when extending a base image with a Packer `openhpc-extra` build, the base image must have `ansible-init` installed but not existing K3s instances.
8+
idempotent and changes to variables will not be reflected in the image when running `site.yml`.

0 commit comments

Comments
 (0)