fix: remove extraSecrets mySecret blocking KBS deployment#88
Merged
butler54 merged 1 commit intoMay 28, 2026
Merged
Conversation
The mySecret entry in extraSecrets was accidentally included in PR validatedpatterns#85 and is preventing KBS from deploying. The trustee-operator fails every ~17 minutes with: 'Secret "mySecret" not found' Without KBS deployment: - No attestation service available - All kata pods fail with CDH errors: 'Get resource failed' - hello-openshift secure/insecure pods: CreateContainerError - kbs-access secure pod: Init:CreateContainerError This is a production blocker affecting all confidential workloads. Fixes validatedpatterns#85
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.
Problem
The
mySecretentry inextraSecrets(added in PR #85) is blocking KBS deployment in production. The trustee-operator controller fails every ~17 minutes with:Impact
Production blocker - all confidential workloads failing:
CreateContainerErrorwith CDH error:Get resource failedSolution
Remove the
extraSecrets: [mySecret]section fromoverrides/values-trustee.yaml. This was test configuration that should not have been merged.Testing
Verified on live Azure cluster running from main:
After this fix merges, cluster sync will deploy KBS and unblock attestation.
Fixes #85