Skip to content

Support OCIRepository for Crossplane installation #41

@maximiliantech

Description

@maximiliantech

What would you like to be added:

Currently, we just support Flux' HelmRepository resource to install Crossplane, see

repo := &sourcev1.HelmRepository{
ObjectMeta: metav1.ObjectMeta{
Name: strings.ToLower(ComponentNameCrossplane),
Namespace: rcontext.TenantNamespace(ctx),
},
Spec: sourcev1.HelmRepositorySpec{
URL: c.ChartSpec.Repository,
Timeout: &metav1.Duration{Duration: 1 * time.Minute},
},
}

In the future we only want to support pulling Helm charts (in general all images, charts etc.) from an OCI registry. There we have to use OCIRepository resources to pull Helm charts.

With the task, we remove the implementation to use HelmRepository and from now on only support OCIRepository resources from Flux. The structure of ProviderConfig API needs to be rewritten in order to match our proposal.

Authentication to private OCI registry is something that needs be taken care of as well, as part of this issue.

Why is this needed:
In some environments where Crossplane might not be stored in Helm repositories but OCI repositories instead, it would come in handy that the service-provider-crossplane supports this out of the box. Important is that the ProviderConfig makes it configurable how the provider should behave.

Metadata

Metadata

Labels

area/open-mcpAll ManagedControlPlane related issues

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions