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

[Release 1.4.0] Clarify the table with the OCI Helm charts #630

Merged
merged 1 commit into from
Nov 28, 2024

Conversation

maelvls
Copy link
Member

@maelvls maelvls commented Nov 25, 2024

Olu and I found that the table was out of date and didn't reflect the real flow.

For context, the real OCI helm chart flow is as follows:

v1.1.0 (Git tag in the jetstack-secure repo)
 └── oci://quay.io/jetstack/charts/venafi-kubernetes-agent --version 1.1.0 (GitHub Actions in the jetstack-secure repo)
    ├── oci://us.gcr.io/jetstack-secure-enterprise/charts/venafi-kubernetes-agent (Enterprise Builds's GitHub Actions)
    └── oci://eu.gcr.io/jetstack-secure-enterprise/charts/venafi-kubernetes-agent (Enterprise Builds's GitHub Actions)
        ├── oci://registry.venafi.cloud/charts/venafi-kubernetes-agent --version 1.1.0 (Harbor Replication)
        └── oci://private-registry.venafi.cloud/charts/venafi-kubernetes-agent --version 1.1.0 (Harbor Replication)
        └── oci://private-registry.venafi.eu/charts/venafi-kubernetes-agent --version 1.1.0 (Harbor Replication)

After being pushed to oci://quay.io/jetstack/charts/venafi-kubernetes-agent by the jetstack-secure's repo's GitHub action, the OCI Helm chart goes through two levels of synchronization:

  1. First level: it gets synced GitHub Action release_enterprise_builds.yaml every days at 7:00am UK time.
  2. Second level: it gets synced by Harbor's private-img-and-chart-replication.tf every 30 minutes.

You can speed up the first level by have manually triggering release_enterprise_builds.yaml.

@maelvls maelvls requested a review from wallrj November 25, 2024 15:16
Copy link
Contributor

@SgtCoDFish SgtCoDFish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

Looks like a good improvement to me!

@maelvls maelvls merged commit 3e62412 into master Nov 28, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants