Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
b
brainy-electrician-41196
08/31/2022, 7:07 PMis there a full example of k3s config.yaml? https://rancher.com/docs/k3s/latest/en/installation/install-options/#:~:text=An%20example%20of%20a%20basic%20server%20config%20file%20is%20below%3A
c
creamy-pencil-82913
08/31/2022, 8:32 PMno. any CLI flag is a valid key in config.yaml. The config file is literally just translated to CLI flags during startup.
so if you look at the server or agent docs, or run
k3s server --helpb
brainy-electrician-41196
08/31/2022, 8:34 PMgotcha, thanks for the tip 🙂
also
is this still valid?
kube-controller-manager-arg:
- "address=0.0.0.0"
- "bind-address=0.0.0.0"
kube-proxy-arg:
- "metrics-bind-address=0.0.0.0"
kube-scheduler-arg:
- "address=0.0.0.0"
- "bind-address=0.0.0.0"
etcd-expose-metrics: truetrying to switch from systemd service flags to that config file
disable:
- "traefik"
- "local-storage"
flannel-backend: "none"
etcd-s3-endpoint: "<http://s3.us-west-000.backblazeb2.com|s3.us-west-000.backblazeb2.com>"
etcd-s3-access-key: "xxxxx"
etcd-s3-secret-key: "yyyyy"
etcd-s3-bucket: "k3s-etcd"
etcd-s3-region: "us-east-1"
kube-controller-manager-arg:
- "address=0.0.0.0"
- "bind-address=0.0.0.0"
kube-proxy-arg:
- "metrics-bind-address=0.0.0.0"
kube-scheduler-arg:
- "address=0.0.0.0"
- "bind-address=0.0.0.0"
etcd-expose-metrics: truec
creamy-pencil-82913
08/31/2022, 8:51 PMyeah that all looks fine
b
brainy-electrician-41196
08/31/2022, 8:51 PMshould be, but apparently
address=bind-address=c
creamy-pencil-82913
08/31/2022, 8:54 PMI mean, they do have to be valid arguments for those components
you can put whatever args you want in there, k3s doesn’t validate them, just passes them through to Kubernetes
if you try something that doesn’t exist, or give it a bad value, it will probably blow up
b
brainy-electrician-41196
08/31/2022, 8:55 PMi did
and it does 🙂
btw, thanks so much for the help
this is what i was coming from https://github.com/k3s-io/k3s/issues/3619#issuecomment-878501106
c
creamy-pencil-82913
08/31/2022, 9:30 PMyeah, be careful copy-pasting stuff out of comments… not everyone that suggests something knows what they’re doing lol
b
brainy-electrician-41196
08/31/2022, 9:33 PMa significant amount of my homelab is probably copy paste from github issue comments
but then again my downtime doesnt cost me anything
uuuuuuuh
i'm using argocd to manage stuff in my cluster
is there a way to codify k3s config in a repo and have argocd apply it?
maybe with system-upgrade-controller?
c
creamy-pencil-82913
08/31/2022, 9:43 PMNot really… SUC is more about upgrading the binary.. for host configuration management I think people usually use things like ansible/puppet/teraform?
b
brainy-electrician-41196
08/31/2022, 9:44 PMyea, that sounds reasonable