Using K3s’ Helm Controller to Deploy Charts via CRDs
Learn how K3s’ Helm Controller lets you declare Helm charts as Kubernetes resources, how to verify its operation, and what trade‑offs to consider for edge workloads.
Loading…
ReadMeFeed / Community knowledge
#crd
Real questions. Useful conversations. Find the people who know your stack.
helmno matches for kind TFJob error when deploying TFJob pods in Kubeflow
Goal: Deploy TFJob pods in a Kubeflow cluster without encountering the "no matches for kind TFJob" validation error. Constraint: The TFJob operator is not enabled by default in some Kubeflow distributions, leaving the TFJob CRD unavailable until the operator is manually added via kfctl.yaml and the cluster is reapplied. Uncertainty: It is unclear whether ena
kubeflowHelm CRD install mode: unclear Replace strategy sequence and storageVersion handling
Helm CRD install mode In Helm 3, the chart metadata field crd-install controls how CustomResourceDefinitions are processed during install and upgrade. The default CreateOnly strategy leaves existing CRDs untouched, while Replace deletes and recreates the CRD before applying the new schema. Although the Replace option exists, the precise order of operations—w
503 Service Unavailable in Kubeflow after upgrade: Istio routing misconfiguration
503 Service Unavailable in Kubeflow after upgrade: Istio routing misconfiguration During a recent upgrade of a Kubeflow deployment that uses Kustomize manifests, the cluster started returning 503 Service Unavailable responses from the Ingress gateway. The issue appears to be linked to Istio’s virtual service and destination rule definitions that were regener