-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
5
-
False
-
False
-
Undefined
-
https://github.com/redhat-developer/service-binding-operator/pull/1132, https://github.com/redhat-developer/service-binding-operator-helm-chart/pull/1, https://github.com/redhat-developer/service-binding-operator-helm-chart/pull/2, https://github.com/redhat-developer/service-binding-operator-helm-chart/pull/3
-
-
AppSvc Sprint 217, AppSvc Sprint 218
Use helm charts for deploying Service binding operator instead of depending on the existence of the OLM on the cluster.
Upstream Documentation Required
- is related to
-
APPSVC-1147 Remove the dependency on creating a secret containing kubeconfig when testing sbo helm chart
-
- Backlog
-
- relates to
-
APPSVC-1118 Handle the cert manager dependency for the Service Binding Operator Helm chart
-
- New
-
-
APPSVC-1113 Automate the process for releasing a new version for SBO Helm chart
-
- Backlog
-
-
RHDEVDOCS-4000 [SB] Review Kartikey's upstream content on Creating Helm chart to deploy Service Binding Operator
-
- Closed
-
-
APPSVC-1117 Update the Service Binding Operator Chart Readme and upstream docs as per review comments from doc team
-
- Closed
-
-
RHDEVDOCS-3561 [SB] Document about the distribution of SBO as an Helm Chart
-
- Closed
-