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
bland-painting-61617
07/17/2022, 4:13 PMIs it just me thinking that the documentation of Rancher and K3s is written by someone who thinks we all know how it works or are we supposed to dig into code to know? For example:
--etcd-s3-endpoint-ca value (db) S3 custom CA cert to connect to S3 endpointBase64 pem it is thanks to source code 🤓
b
busy-crowd-80458
07/18/2022, 6:26 PMNot just you, I definitely get that impression too.
I appreciate Rancher and k3s as products, but documentation could use less assumptions.
😅 1
Then again, that's true for most Kubernetes software.