Only enable wiz broker components on non eks clusters #9724
+10
−1
Conversation
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
hagenmathis
added
bugfix
hagenmathis
force-pushed
the
disable-wiz-on-eks
branch
4 times, most recently
from
0363453 to
e7c0938
Compare
hagenmathis
force-pushed
the
disable-wiz-on-eks
branch
from
e7c0938 to
33ae74f
Compare
hagenmathis
force-pushed
the
disable-wiz-on-eks
branch
from
33ae74f to
ccf32a2
Compare
|
👍 |
hagenmathis
changed the title
hagenmathis
changed the title
zaklawrencea
approved these changes
Aug 11, 2025
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.
Reopening #9662 to debug the error in the e2e tests. From the original PR:
makes the default config items conditional to only deploy the broker and its associated resources to non eks clusters. Neither broker nor connector should be needed with eks, as access to Wiz is granted using access entries