revert: registry.access.redhat.com override + use debug-initdata for kbs-access-sealed - #144
Merged
butler54 merged 2 commits intoSep 2, 2026
Conversation
kbs-access-curl already mounts the debug-initdata ConfigMap (both the coco.io/initdata-configmap annotation and the initdata volume). Switch kbs-access-sealed to the same debug-initdata ConfigMap for consistency between the two kbs-access test workloads. Both initdata and debug-initdata are generated by the same init-data-gzipper.yaml playbook, and the RVPS init_data reference value already includes both variants' hashes (see rvps-values-policies.yaml's init_data entry: pcr8Hash, debugPcr8Hash, rawHash, debugRawHash), so this does not affect attestation.
butler54
changed the title
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
1 participant
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.
What
1. Reverts #141 (
8c2aa7e), which addedoverridesblocks tovalues-azure.yamlpointinghello-openshift,kbs-access-curl, andkbs-access-sealedatregistry.access.redhat.com/ubi9/httpd-24@sha256:68a91ff6...instead of the chart default (
registry.redhat.io/ubi9/httpd-24, samedigest/content).
This is a clean
git revertof 8c2aa7e — no conflicts, removes exactly the16 lines that PR added and nothing else.
values-azure.yaml's workloadimages go back to the chart's default
registry.redhat.ioreference onconnected Azure.
Scope: connected Azure (
values-azure.yaml) only, matching the scope of theoriginal change — baremetal and the Azure spoke/mirror topologies were never
touched by #141 and are unaffected by this revert.
2.
kbs-access-sealednow usesdebug-initdata, matchingkbs-access-curl(which already mountsdebug-initdatavia both thecoco.io/initdata-configmapannotation and theinitdatavolume). Bothinitdataanddebug-initdataConfigMaps are generated by the sameansible/init-data-gzipper.yamlplaybook, and the RVPSinit_datareference value already includes both variants' hashes (see
rvps-values-policies.yaml'sinit_dataentry:pcr8Hash,debugPcr8Hash,rawHash,debugRawHash), so this doesn't affect attestation — it justmakes the two kbs-access test workloads consistent with each other.