-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lack of documentation when kubectl explain
#1685
Comments
Thanks for reporting this. This is definitely something we're interested in merging, but currently not our highest priority. If you have the time, we'd appreciate a PR. Otherwise, this will have to wait until one of us has some downtime |
Revisiting this issue, I've checked against my installation where descriptions are present. How did you install the operator to test this? We had issues with missing descriptions before, so I'd like to make sure they are still present in all installation methods (see #1567 for context) |
@theSuess thanks. I will check and report back to you. |
@theSuess So I found the reason. https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#some-caveats-and-explanations
The tools like FluxCD and ArgoCD solves this issue with their own features. Like https://fluxcd.io/flux/components/helm/helmreleases/#controlling-the-lifecycle-of-custom-resource-definitions I think the issue could be closed as there is no good solution for upgrading CRDs with current tools. |
Yeah, it really sucks that helm doesn't do CRD updates. We have the full instructions for manual upgrades in our documenation: https://grafana.github.io/grafana-operator/docs/installation/helm/#upgrading Thanks for taking a closer look at what caused this in your case! |
Like a DevOps I expect that
kubectl explain GrafanaDashboard.spec.datasources
would give me some meaningful output. Right not it returnsIt is very basic information. I'd like to see the documentation like for the embedded k8s api resources:
or good and mature operators like FluxCD:
The text was updated successfully, but these errors were encountered: