Fix warning on OCP 4.11 cluster for operator install
Operator make apply is throwing warning on new OCP 4.11 cluster because of the restricted PSA getting available by default
This will fix the warning on 4.11
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you review them:
- [ ] Includes tests (if functionality changed/added)
- [ ] Includes docs (if user facing)
- [x] Commit messages follow commit message best practices
See the contribution guide for more details.
Release Notes
Fix warning on OCP 4.11 cluster for operator install
shall we also this to all deployments created by operator? if the deployment doesn't have it..
shall we also this to all deployments created by operator? if the deployment doesn't have it..
I tested and checked, and it is happening for all components deployment also. How do we want to handle this? Through transformer or have it got added in different components etc? cc @sm43 @nikhil-thomas @vdemeester
shall we also this to all deployments created by operator? if the deployment doesn't have it..
I tested and checked, and it is happening for all components deployment also. How do we want to handle this? Through transformer or have it got added in different components etc? cc @sm43 @nikhil-thomas @vdemeester
Probably yes. We need to ensure we have those set correctly on the thing we support, no matter what upstream does.
/grooming
@piyush-garg interesting, it doesn't look like "root" label work with the command...
maybe we could have a triage one ? 🤔
/triage grooming
/triage wg-discuss This one seems to exist 🤔
/project "Tekton Operator working group"
@vdemeester: There is no maintainer team for this repo or org.
In response to this:
/project "Tekton Operator working group"
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
shall we merge this? @piyush-garg and handle for components in another pr ? or are you gonna update this one?
shall we merge this? @piyush-garg and handle for components in another pr ? or are you gonna update this one?
I am updating this one
@piyush-garg what is the status here ?
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: vdemeester
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [vdemeester]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/lgtm
/cherrypick release-v0.60.x
@concaf: new pull request created: #1083
In response to this:
/cherrypick release-v0.60.x
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.