Skip to content

Commit

Permalink
Add troubleshooting note for k3s HelmChart
Browse files Browse the repository at this point in the history
Follow-up to cover common likely issue noticed while attempting to debug
a red-herring issue in fluxcd/source-controller#831

Signed-off-by: Kingdon Barrett <kingdon@weave.works>
  • Loading branch information
Kingdon Barrett committed Jul 14, 2022
1 parent a99f852 commit 0203ea4
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions content/en/docs/cheatsheets/troubleshooting.md
Expand Up @@ -52,6 +52,12 @@ kubectl get helmreleases.helm.toolkit.fluxcd.io -A
kubectl get helmcharts.source.toolkit.fluxcd.io -A
```

{{% alert color="warning" title="HelmCharts and HelmReleases CRDs conflict with other Helm controllers" %}}
When a `HelmRelease` exhibits the issue `HelmChart 'podinfo/podinfo-podinfo' is not ready`, a common issue on k3s clusters or other environments that bundle a different Helm controller is caused by a conflict between these CRDs when they are used without fully qualifying.

For example: `kubectl get helmcharts` can access the wrong CRD and users may be fooled into thinking that a `HelmChart` resource was not created successfully. To avoid this issue, use the alternative `flux get source chart` or fully qualify when using `kubectl get` as shown above.
{{% /alert %}}

Looking for controller errors:

```cli
Expand Down

0 comments on commit 0203ea4

Please sign in to comment.