-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pod history toggling issue #111
Pod history toggling issue #111
Conversation
d4265b1
to
58807da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/hold
Squash the commits, and I'll be happy 👍
cb0fa89
to
affe52e
Compare
58807da
to
55b8734
Compare
Signed-off-by: Yi Rae Kim <yikim@redhat.com>
55b8734
to
17f2d1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JustinKuli, yiraeChristineKim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description of problem: When Pod security policy is created and the status is changed from inform to enforce, the status is toggling. Not able to enforce pod security policy. How to fix Set default value when Kube API value omitted ref: https://issues.redhat.com/browse/ACM-3109 Signed-off-by: Yi Rae Kim <yikim@redhat.com> (cherry picked from commit b70748b)
Description of problem:
When Pod security policy is created and the status is changed from inform to enforce, the status is toggling. Not able to enforce pod security policy.
How to fix
Set default value when Kube API value omitted
ref: https://issues.redhat.com/browse/ACM-3109