refined-magician-25478
05/13/2022, 3:48 PMcreamy-pencil-82913
05/13/2022, 3:53 PMrefined-magician-25478
05/13/2022, 3:57 PMcreamy-pencil-82913
05/13/2022, 4:02 PMrefined-magician-25478
05/13/2022, 4:13 PMhelm template
to convert 2 helm charts, Weave and Docker Registry. I tried this approach with Certificate Manager although it silently fails to install. The CRD's are created but the pods are not listed. I am able to helm install it and deploy it using kubectl apply
on the manifest files that I placed in the manifest directory. Ranchers documentation says that manifests are deployed "similar to kubectl apply
". Are there any differences between kubectl apply
and Ranchers approach that should be noted?creamy-pencil-82913
05/13/2022, 4:22 PMhelm template
to flatten the charts to manifests and then just dropping those in the manifests dir you should be fine. We only touch things that contain a HelmChart resource. It is pretty much the same as just running an apply in a retry loop. Check the service logs and kubectl describe addon
output for errors.helm template
extra CLI flags to get them included.refined-magician-25478
05/13/2022, 4:40 PMkubectl apply
. By service logs do you mean the service that I am attempting to start? I'll check kubectl describe addon
but are there any other logs that you would recommend looking at other than the rke2 systemd logs?kubectl describe addon
listed the CRDs that I would expect that relate to the service but nothing else that was relevant. The expected pods don't show up when running kubectl get pods --all-namespaces
. When I delete the CRDs, then run kubectl apply <service manifest files dir> --recursive
everything comes up as expected. Maybe I need to look into the --recursive
option more based on the way rke2 is "running apply in a retry loop".creamy-pencil-82913
05/13/2022, 5:09 PMrefined-magician-25478
05/13/2022, 5:11 PM