KATA-1374: Create monitor daemonset post runtimeclass creation #183
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.
Fixes: #KATA-1374
- Description of the problem which is fixed/What is the use case
When creating KataConfig and observing the PODs under openshift-sandboxed-containers-operator namespace it shows huge number of restarts (20+) for monitor PODs.
- What I did
Updated the logic to create monitor DS post runtimeclass creation
- How to verify it
Create Kataconfig and observe the POD status under openshift-sandboxed-containers-operator namespace
- Description for the changelog
Create monitor daemonset post runtimeclass creation