-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathuser-values.yaml
59 lines (51 loc) · 2.01 KB
/
user-values.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
# ===================== Mandatory Values =======================
# This is required, a user can pre-allocate a floating IP and set it here
# to be used by the cluster. If this is not set, a new floating IP will be
# allocated for the cluster each time it is created and clusters cannot .
apiServer:
floatingIP: ""
# --------------------------- Optional Values -------------------------
# List of comma separated additional packages to install on cluster nodes
additionalPackages: []
controlPlane:
# The number of control plane machines to deploy
# For high-availability, this should be greater than 1
# For etcd quorum, it should be odd - usually 3, or 5 for very large clusters
machineCount: 5
# The flavor to use for control plane machines
machineFlavor: l3.nano
# defaults cause OutofSync issues in argocd
remediationStrategy:
retryPeriod: 20m0s
minHealthyPeriod: 1h0m0s
# The Kubernetes version of the cluster
# This should match the version of kubelet and kubeadm in the image
# and will be automatically updated by us
kubernetesVersion: "1.30.6"
# The name of the image to use for cluster machines
machineImage: "capi-ubuntu-2204-kube-v1.30.6-2024-11-15"
addons:
# Monitoring sets up kube-prometheus-stack and loki-stack.
# Monitoring is disabled by default because of cinder issues
monitoring:
enabled: false
# Ingress is preferred, as it allows you to use DNS to locate multiple
# services behind a single FIP, and makes TLS trivial
# see https://stfc.atlassian.net/wiki/spaces/CLOUDKB/pages/309854262/CAPI+Ingress
ingress:
enabled: false
nginx:
release:
values:
controller:
service:
loadBalancerIP: # "130.x.y.z"
# Settings for node-level registry auth if using a private registry
registryAuth:
{}
# registry-1.docker.io:
# username: "<username>"
# password: "<password>"
# The name of the SSH key to inject into cluster machines, this can be
# left blank if a user does not require SSH access to the machines
machineSSHKeyName: