You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine we try to install kube-prometheus-stack. It has some CRDs defined and also some resources that use it.
Since we try to run dry-run install to get manifests, it fails (no CRDs are deployed yet).
Right now there is one workaround for this: offline_kube_version. It is required only during first install.
The proposal is:
Either automatically enable offline_kube_version if we get the error and retry
Or discover CRDs in the release and try to hack kube mapping to include those CRDs
The text was updated successfully, but these errors were encountered:
Imagine we try to install kube-prometheus-stack. It has some CRDs defined and also some resources that use it.
Since we try to run dry-run install to get manifests, it fails (no CRDs are deployed yet).
Right now there is one workaround for this:
offline_kube_version
. It is required only during first install.The proposal is:
offline_kube_version
if we get the error and retryThe text was updated successfully, but these errors were encountered: