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
m
millions-alarm-86298
05/06/2022, 9:03 AMskaffold + k3d is unbeatable combo for CI / CD and e2e testing of helm charts
very smoothly running on GH Actions and allows doing "crazy things" 😉
🙏 1
🎉 1
w
wide-garage-9465
05/06/2022, 9:04 AMThank you very much for the amazing feedback 🙂
m
millions-alarm-86298
05/06/2022, 9:06 AMthnx for the great tool @wide-garage-9465
❤️ 1
w
wide-garage-9465
05/06/2022, 9:54 AMThank you very much for your support ❤️
g
green-musician-2686
05/06/2022, 11:09 AM@millions-alarm-86298 fancy a blog about your experience ? 🙂
m
millions-alarm-86298
05/06/2022, 11:23 AMrather no 🙂 it's too difiicult for me 🙂
g
green-musician-2686
05/06/2022, 12:43 PMwhat is the value of skaffold in this combo ?
m
millions-alarm-86298
05/06/2022, 1:25 PM• build images passing env vars to BuildKit
• use local registry (provided by k3d) in CI instead of publishing in each build to dockerhub or smth
• parametrizing chart with values depending on env
• simpler start / stop of helm chart thatn actually using helm
• finally build and publish dockers to real regstry
that's how I use it, but there are more scenarios other pplz use
g
green-musician-2686
05/06/2022, 3:12 PMbut when you run k3d as local registry in CI - how do you make it persistent 🤔
m
millions-alarm-86298
05/06/2022, 7:50 PMhmmm
i don't understand the question, plz re-phrase
g
green-musician-2686
05/09/2022, 8:24 AMI am referring to this point:
use local registry (provided by k3d) in CIm
millions-alarm-86298
05/09/2022, 7:49 PMyes, exactly
CI images not published to dockerhub on every run,
i can leverage k3d registry for regular CI builds and still be able to use those image in my charts
and publish to dockerhub only in release job
g
green-musician-2686
05/10/2022, 8:00 AMI am not sure what CI you are using but in our case (Gitlab) we would need to "share" artifacts (read: push to and pull from the gitlab server). I wonder how you keep k3d persistent between CI tasks/jobs. Any magic ?
m
millions-alarm-86298
05/10/2022, 8:03 AMi don't keep them because I don't need them
i only need a registry during a CI job run
1. build a docker and push to local registry
2. start my helm chart with local images
3. test helm chart
4. shutdown k3d + registry
such proceses happend dozen time a day for dozens of repositories
we would kill gitlab / github / dockerhub registry if we publish all those temp images there
so k3d + local registry is a life saver
g
green-musician-2686
05/10/2022, 10:49 AMso in the same pipeline you build and push the docker image to k3d-based registry and then deploy helm chart with this image to the same k3d ?
m
millions-alarm-86298
05/10/2022, 11:19 AMyes
g
green-musician-2686
05/10/2022, 12:59 PMthanks