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
Powered by
Title
m
millions-alarm-86298
05/10/2022, 5:39 PM
Hi all I never used
internal k3d
traefik before, so encountered an issue when creating a new cluster with LB and traefik the
k3d cluster create
doesn't wait until traefik is up , so I manually must check if helm chart and CRDs are installed is there any way to improve this experience ?
c
creamy-pencil-82913
05/10/2022, 5:50 PM
retry until it succeeds is generally the Kubernetes “eventually consistent” way of doing things
2 Views
#k3d
Join Slack