Remove the "operator" init container #1558
Merged
Conversation
This file contains 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
44dd441 to
6fdff09
Compare
jrfastab
approved these changes
Oct 9, 2023
4e5fa95 to
4361e26
Compare
- Remove the "operator" init container. Now there is a proper operator deployment, so we don't need to create CRDs in the init container. - Update the Tetragon daemonset ClusterRole accordingly. - Modify the Tetragon daemonset initialization logic to wait for all the required CRDs to show up before proceeding. Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
4361e26 to
bbefaba
Compare
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.
deployment, so we don't need to create CRDs in the init container.
required CRDs to show up before proceeding.
Signed-off-by: Michi Mutsuzaki michi@isovalent.com