-
Notifications
You must be signed in to change notification settings - Fork 503
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
Bug 1978798: Update ovnKubernetesConfig.policyAuditConfig Default #993
Bug 1978798: Update ovnKubernetesConfig.policyAuditConfig Default #993
Conversation
@astoycos: This pull request references Bugzilla bug 1978798, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
/assign @sttts |
@@ -239,6 +239,7 @@ spec: | |||
policyAuditConfig: | |||
description: policyAuditConfig is the configuration for network policy audit events. If unset, reported defaults are used. | |||
type: object | |||
default: null |
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.
this looks wrong. What is kubebuilder doing here?
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.
Not sure Maybe I need to specify the object here? Let me give that a try.
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.
Two ways to solve this:
- fix kubebuilder's controller-gen upstream
- use a yaml patch as we do in similar cases where kubebuilder is broken. Look in this repo for yaml-patch files as blueprint. A yaml patch allows you to set
{}
here explicitly as value. It is applied after controller-gen has been run.
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.
+1 sounds good I'll give a stab at debugging kubebuilder first, thanks!
/bugzilla refresh The requirements for Bugzilla bugs have changed, recalculating validity. |
@openshift-merge-robot: This pull request references Bugzilla bug 1978798, which is invalid:
Comment In response to this:
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. |
889a5f7
to
78c2313
Compare
@sttts I bashed my head against kubebuilder for a while trying to fix this, however based on the design of controller-tools it doesn't seem like a very trivial thing to fix. I opened kubernetes-sigs/controller-tools#622 and asked for help in upstream/ and downstream slack channels to no avail. :( For now I'd like to get this bug fixed with the following patch and then fix properly upstream once I can get more help/time. |
78c2313
to
5efff77
Compare
/lgtm |
Rename the Cluster Network Operator's CRD so that a post schema generation patches can be used on the generated CRD Shema Signed-off-by: astoycos <[email protected]>
5efff77
to
aeb12f5
Compare
Sounds good I'll fix these... Also when I changed the naming to |
The patch tool uses another library to format the yaml. So that's expected, ugly, but expected. |
We need to initialize `ovnKubernetesConfig.policyAuditConfig` so that the proper defaults are populated when a CNO config object is created It would be better to do this using the `+kubebuilder:default` flag however it is broken for this case as described in this [upstream issue](kubernetes-sigs/controller-tools#622) Signed-off-by: astoycos <[email protected]>
aeb12f5
to
6f0ce8c
Compare
ACK I though I did something wrong :) Removed the comments, should be good to go |
/bugzilla refresh |
@astoycos: This pull request references Bugzilla bug 1978798, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
/lgtm |
@astoycos: All pull requests linked via external trackers have merged: Bugzilla bug 1978798 has been moved to the MODIFIED state. In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astoycos, sttts 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 |
/cherry-pick release-4.9 |
/cherry-pick release-4.8 |
@astoycos: new pull request created: #1014 In response to this:
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. |
@astoycos: #993 failed to apply on top of branch "release-4.8":
In response to this:
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. |
/cherry-pick release-4.9 |
@astoycos: new pull request could not be created: failed to create pull request against openshift/api#release-4.9 from head openshift-cherrypick-robot:cherry-pick-993-to-release-4.9: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-993-to-release-4.9."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} In response to this:
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. |
We need to initialize
ovnKubernetesConfig.policyAuditConfig
so that the proper defaults are populated when a CNO config
object is created
Signed-off-by: astoycos [email protected]