Skip to content

chore: update documentation to oci registry #716

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

Merged
merged 2 commits into from
Mar 5, 2025

Conversation

xeniape
Copy link
Member

@xeniape xeniape commented Feb 28, 2025

Part of https://github.com/stackabletech/infrastructure/issues/142
Updates references to oci registry and adjusts documentation on images and image lookup.

Copy link

netlify bot commented Feb 28, 2025

Deploy Preview for stackable-docs ready!

Name Link
🔨 Latest commit 5333368
🔍 Latest deploy log https://app.netlify.com/sites/stackable-docs/deploys/67c84f00874df600083b9f83
😎 Deploy Preview https://deploy-preview-716--stackable-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@xeniape xeniape moved this to Development: Waiting for Review in Stackable Engineering Feb 28, 2025
@xeniape
Copy link
Member Author

xeniape commented Mar 4, 2025

Release Note

Starting with this release SDP operators, product image selection and tools, like stackablectl, use oci.stackable.tech (OCI registry) as the default image registry instead of docker.stackable.tech.
To ease the transition, operator and product images, as well as operator Helm Charts, will be pushed to both registries for this release, but only tooci.stackable.tech in subsequent releases.
To keep using the docker.stackable.tech registry during this time for products, set the spec.image.repo property to docker.stackable.tech/stackable in the respective product CR.
To configure stackablectl to pull Helm Charts from the old registry, use --chart-source repo in the operator install commands. Unfortunately, those Helm Charts are using values, which specify the repository for the images to be the OCI registry and it is not possible to edit or override those values using stackablectl.
Instead, if the image repository for the operators themselves also needs to be docker.stackable.tech, use the helm install command and provide an image.repository value to override the default one. For example for airflow-operator:

helm repo add stackable-stable https://repo.stackable.tech/repository/helm-stable/
helm repo update stackable-stable
helm install --wait airflow-operator stackable-stable/airflow-operator --version 25.3 --set image.repository=docker.stackable.tech/stackable/airflow-operator

sbernauer
sbernauer previously approved these changes Mar 5, 2025
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

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

Thanks for updating and writing the guide!

@sbernauer sbernauer moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Mar 5, 2025
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

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

Thanks!

@xeniape xeniape added this pull request to the merge queue Mar 5, 2025
Merged via the queue into main with commit aeeb9a2 Mar 5, 2025
7 checks passed
@xeniape xeniape deleted the chore/update-documentation-to-oci-registry branch March 5, 2025 13:22
@sbernauer sbernauer moved this from Development: In Review to Development: Done in Stackable Engineering Mar 10, 2025
@lfrancke
Copy link
Member

Do we have any harbor related issue with a release note snippet?

@lfrancke lfrancke moved this from Development: Done to Acceptance: In Progress in Stackable Engineering Mar 20, 2025
@xeniape
Copy link
Member Author

xeniape commented Mar 20, 2025

Do we have any harbor related issue with a release note snippet?

Yes, this one 😄 #716 (comment)

@xeniape xeniape added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Mar 26, 2025
@lfrancke lfrancke moved this from Acceptance: In Progress to Done in Stackable Engineering Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/25.3.0 release-note Denotes a PR that will be considered when it comes time to generate release notes.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants