input stringclasses 6
values | output stringclasses 6
values |
|---|---|
K3s cluster bootstrap
Bootstrap with Puppet
Puppet configuration
Cluster initialization
CI job
Input
Outputs
Operations
Create DNS record for cluster access
Create config files for k3s
Start/enable k3s
Output display
Bootstrap with Puppet
Puppet configuration
Inlcude the kbi::k3s module, and set the following paramete... | Create DNS record for cluster access |
You can either:
do that in order: by beginning by the initiator controller, then running puppet on all other controllers, then all workers once it has finished.
Q: What is the first step to do?
Referring to the passage above, the correct answer to the given question is | beginning by the initiator controller |
I know that the answer to the question "What is the main point of the text?" is in "not caring and running it on all of them at the same time: some services will fail at first but will retry until the initiator has finished, ultimately all nodes will join the cluster.". Can you tell me what it is? | not caring and running it on all of them at the same time |
CI job
Input
customer : String
Ex: ig1
project : String
Ex: kbilab
server_nodes : Array[String]
A list of FQDNs of controller nodes
Ex:
agent_nodes : Array[String]
A list of FQDNs of worker nodes
Ex:
k3s_version : String
Ex: 1.28.3+k3s2-ig1~1+bookworm
cluster_cidr : Optional[String]
Default: 10.96.0.0/16
service_cidr :... | /data/k3s/local-storage |
Refer to the passage below and answer the following question:
Passage: Special cases to handle:
Outputs
Operations
Create DNS record for cluster access
Push a DNS record to Route53 with an RR to all controllers.
Question: What is one special case to handle? | Outputs |
Create config files for k3s
for each server:
/etc/rancher/k3s/config.yaml :
/etc/default/k3s :
for each agent:
/etc/rancher/k3s/config.yaml :
/etc/default/k3s :
Start/enable k3s
enable service k3s.service
start service k3s.service
Output display
DNS record of all controllers
聽
聽
only 1 controller
1
---
2
cluster-cidr: ... | /etc/rancher/k3s/config.yaml |
README.md exists but content is empty.
- Downloads last month
- 3