Support for pre-deploy validation webhooks. #6780
Labels
kind/proposal
An issue that reports a new feature proposal to be discussed
stale
Automatic label to stale issues due inactivity to be closed if no further action
Milestone
Summary
kubeapps should support an optional pre-deploy validation webhook, that DevOps (admin of kubeapps, charts, or kubernetes cluster) can be used to integration various workflows that suits their team. The validation webhook is triggered after user selects chart and provided values, but before actually deploys. The webhook should return with "ok" or "not ok", providing contexts on the reason as necessary, to be displayed on kubeapps UI.
Background and rationale
Some scenarios where this can be useful:
Description
A pre-deploy validation webhooks can be provided to kubeapps configurations. If provided...
After user selects a package, before actually deploys, user will need to click a "validate" button, which triggers the pre-deploy webhook.
Relevant information will be passed to the webhook, e.g. user, cluster, namespace, chart, user-provided values
The webhook is expected to return some status such as "ok" or "error", along with additional information in the payload.
The additional information is displayed in the kubeapps UI, so user knows what to do when "not ok"
User can only click "Deploy" after webhook returns "ok"
The text was updated successfully, but these errors were encountered: