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.
Objective:
Let the user select their own Security Context.
User story:
This has been a constant problem while working with the customers, each customer is using and having different constraints and each time we try to enforce a value in this field, Operator can't be installed and our effort to help them it is a failure when using OperatorHub. And we end up using Kustomize or Helm to be able to debug and get our Pods running under different scenarios and requests. So even when this might look like a good idea, is not giving the flexibility needed for us to let them pick their values based on their own SCC. So please, allow me to get this field removed for the catalogs to work!.