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
Is your feature request related to a problem? Please describe.
Currently, if there's an issue with a HelmChart or HelmRelease, a user will generally have to engage a Cluster Admin who has permissions to be able to ascertain what the issue with the underlying Helm release might be. However, it would be useful if the status of the Helm Release (including / specifically the Helm Job's logs, which would show what the error is) are accessible by a Project Owner or Project Member as well.
Describe the solution you'd like
Unclear; would love user feedback on this issue with examples of use cases and suggestions!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
One possibility is to bubble up Kubernetes events on ProjectHelmCharts that show the current status of the underlying Helm release by parsing the underlying Helm release secret.
Is your feature request related to a problem? Please describe.
Currently, if there's an issue with a HelmChart or HelmRelease, a user will generally have to engage a Cluster Admin who has permissions to be able to ascertain what the issue with the underlying Helm release might be. However, it would be useful if the status of the Helm Release (including / specifically the Helm Job's logs, which would show what the error is) are accessible by a Project Owner or Project Member as well.
Describe the solution you'd like
Unclear; would love user feedback on this issue with examples of use cases and suggestions!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: