Owner: Architect:

Story (Required)

As an OpenShift developer, I will like to be able create Helm repos on my project without the need for administrator permissions to be able to make use of the Helm ecosystem while scoping the availability to my project.

Background (Required)

Right now we support Cluster scoped Helm repo CRDs: https://github.com/openshift/api/blob/master/helm/v1beta1/0000_10-helm-chart-repository.crd.yaml#L17

The workflow for the developers that want to use Helm in Dev Console includes adding a cluster scoped repo using administrator rights. We will like to add the ability to create similar resource but scoped to the namespaces: scope: Namespaced

Glossary

NA

Out of scope

Changing the cluster scope CRD

In Scope

We should create a completely new CRD but scoped to namespaces. Similar to how Role CRD and ClusterRole and Role types have same fields but diff scope. h2.

Approach(Required)

Create Enhancement Request for API change. Once RFE approved, I recommend checking how this was done to add HelmChartRepository. Also see how they implement ClusterRole vs Cluster as well as ClusterRoleBinding vs RoleBinding.

Dependencies

Will require a RFE since it is an OpenShift API change.

Edge Case

Acceptance Criteria

New CRD created: ProjectHelmChartRepository
People are able to create new resource ProjectHelmChartRepository scoped to a namespace.
There is documentation in place in helm section describing the difference between ProjectHelmChartRepository and HelmChartRepository

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied