Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Support for Flux OCI features #309

Closed
kingdonb opened this issue Jul 1, 2022 · 2 comments
Closed

Feature: Support for Flux OCI features #309

kingdonb opened this issue Jul 1, 2022 · 2 comments
Projects
Milestone

Comments

@kingdonb
Copy link
Collaborator

kingdonb commented Jul 1, 2022

Flux has support for HelmRepository objects with type: oci since 0.31.0, released in June.

Flux also has a POC for the Kustomize controller supporting OCI, with a new OCIRepository kind that has only been published in pre-release. It is blocking on the reviews of fluxcd/flux2#2601. We need user and maintainer reviews of this feature to ensure that it is correct before the work on the final implementation can begin.

But for now, we have an implementation of this RFC:

implemented as Proof of Concept in:

We should support the Helm OCI work that has already been released through the stable channel, and the OCIRepository work that is proposed through the prerelease channel of the VSCode extension. 👍 This feature is currently planned for target to release in 0.21.

@kingdonb kingdonb added this to the 0.21 milestone Jul 1, 2022
@kingdonb kingdonb added this to Needs triage in Triage via automation Jul 1, 2022
@kingdonb
Copy link
Collaborator Author

kingdonb commented Jul 2, 2022

Here is the current state (I have an OCIRepository which is not listed in Sources, and a Flux Kustomization which applies from it)

Screen Shot 2022-07-02 at 8 52 10 AM

The flux tree ks river-data-oci looks like:

$ flux tree ks river-data-oci
Kustomization/flux-system/river-data-oci
├── Namespace/default
├── Service/default/river-data
├── Deployment/default/river-data
└── Ingress/default/river-data

It is probably one of these options, as all of the non-OCI things show fine what resources their tree has under them:

sourceRef:
  kind: OCIRepository
  name: river-data-oci
targetNamespace: default

Screen Shot 2022-07-02 at 8 54 10 AM

It still reads the specs OK ☝️

I have not tested against Helm Controller's OCI-based repository source at all (that's next)

The experiment is being run out of here and here:

@kingdonb
Copy link
Collaborator Author

This has landed and is in 0.21.0 🎉

Triage automation moved this from Needs triage to Closed Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Triage
Closed
Development

Successfully merging a pull request may close this issue.

1 participant