Replace the Quay.io references with the OSISM registry - #1069
Merged
Conversation
Container images are no longer pushed to Quay.io, as documented in the "New container registry" section of the OSISM 10 release notes, but two sample `docker ps` listings still showed images pulled from `quay.io/osism`. The manager listing in the troubleshooting guide now shows `registry.osism.tech/osism`. Two of its tags do not exist there and are replaced with tags that do: `kolla-ansible:2023.2` becomes `kolla-ansible:latest`, matching the other images of that listing, and `ceph-ansible:quincy` becomes `ceph-ansible:reef`, the Ceph release OSISM defaults to. The compute node listing in the OpenStack operations guide needed more than the registry. Kolla images now live in a namespace that carries the OpenStack version, so the images move to `registry.osism.tech/kolla/release/2025.1` and the tags are taken from the 20260615 build that OSISM 10.1.0 pins, replacing the 20230919 build of the previous listing. The scaphandre image is unchanged, it is not built by OSISM. Every image reference of both listings was checked against the registry and resolves to an existing manifest. Assisted-by: Claude:claude-opus-5 Signed-off-by: Jan Klare <klare@osism.tech>
✅
|
| Descriptor | Linter | Files | Fixed | Errors | Warnings | Elapsed time |
|---|---|---|---|---|---|---|
| ✅ ACTION | actionlint | 5 | 0 | 0 | 0.08s | |
| ✅ JSON | jsonlint | 4 | 0 | 0 | 0.12s | |
| ✅ JSON | prettier | 4 | 0 | 0 | 0.56s | |
| ✅ JSON | v8r | 4 | 0 | 0 | 8.96s | |
| ✅ MARKDOWN | markdownlint | 168 | 0 | 0 | 2.79s | |
| ✅ MARKDOWN | markdown-table-formatter | 168 | 0 | 0 | 0.41s | |
| ✅ REPOSITORY | betterleaks | yes | no | no | 0.65s | |
| ✅ REPOSITORY | checkov | yes | no | no | 18.88s | |
| ✅ REPOSITORY | git_diff | yes | no | no | 0.09s | |
| ✅ REPOSITORY | secretlint | yes | no | no | 2.16s | |
| ✅ REPOSITORY | trufflehog | yes | no | no | 4.09s | |
| ✅ SPELL | codespell | 178 | 0 | 0 | 0.66s | |
| lychee | 178 | 1 | 0 | 11.19s | ||
| ✅ YAML | prettier | 6 | 0 | 0 | 0.43s | |
| ✅ YAML | v8r | 6 | 0 | 0 | 6.11s | |
| ✅ YAML | yamllint | 6 | 0 | 0 | 0.53s |
Detailed Issues
⚠️ SPELL / lychee - 1 error
📝 Summary
---------------------
🔍 Total.........1045
🔗 Unique.........801
✅ Successful.....984
⏳ Timeouts.........0
🔀 Redirected.......5
👻 Excluded........60
❓ Unknown..........0
🚫 Errors...........1
⛔ Unsupported......1
Errors in docs/guides/configuration-guide/proxy.md
[404] https://about.gitlab.com/blog/2021/01/27/we-need-to-talk-no-proxy/#no_proxy (at 33:4) | Rejected status code: 404 Not Found
Hint: Followed 5 redirects. You might want to consider replacing redirecting URLs with the resolved URLs. Use verbose mode (`-v`/`-vv`) to see redirection details.
Notices
📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)
See detailed reports in MegaLinter artifacts
Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)
- Documentation: Custom Flavors
- Command:
npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Container images are no longer pushed to Quay.io — see the New container registry section of the OSISM 10 release notes — but two sample
docker pslistings still showed images pulled fromquay.io/osism. Those were the onlyquay.iooccurrences left in the repository.troubleshooting-guide/manager.md(manager containers) now showsregistry.osism.tech/osism. Two tags of that listing do not exist on the new registry and are replaced with tags that do:kolla-ansible:2023.2→kolla-ansible:latest, matching the other images of that listingceph-ansible:quincy→ceph-ansible:reef, the Ceph release OSISM defaults tooperations-guide/openstack/index.md(compute node containers) needed more than a registry swap. Kolla images now live in a namespace that carries the OpenStack version, so they move toregistry.osism.tech/kolla/release/2025.1and the tags come from the 20260615 build that OSISM 10.1.0 pins, replacing the 20230919 build of the previous listing.hubblo/scaphandre:0.5.0is unchanged, it is not built by OSISM.Every image reference of both listings — 24 including the Docker Hub ones that were already correct — was checked against the registry with a manifest request and resolves to an existing manifest. Nothing was pulled. markdownlint over both files is clean.
🤖 Generated with Claude Code