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 1809274: crd/kubelet: do not prune kubelet rawExtension fields #1524
Bug 1809274: crd/kubelet: do not prune kubelet rawExtension fields #1524
Conversation
@yuqi-zhang: This pull request references Bugzilla bug 1809274, 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
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.4 |
@yuqi-zhang: once the present PR merges, I will cherry-pick it on top of release-4.4 in a new PR and assign it to you. 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. |
Did some manual validation and can confirm that with the change, the object is no longer being dropped. |
Need a seems sane to me CC: @rphillips |
|
@yuqi-zhang does this mean we also need to update the container runtime cfgs too? |
29f7916
to
f973a16
Compare
Done
I don't believe so. That has a defined set of fields. KubeletConfig was the only rawExtension field in our API |
That said by default I don't think we generate a |
I did some testing and can confirm it does validation on valid |
hmm this is weird for TestKernelType: /test e2e-gcp-op |
/approve |
/lgtm |
/hold @kikisdeliveryservice noted she had a question |
@yuqi-zhang is going to update commit message /hold |
The kubelet config is now validated, but fields are being silently dropped since its an "unknown field" (rawExtension), which by default is pruned by the validator. Some more context, the 2 fields that are being added are from kube specifications, that tell the validator to skip validation as well as mark it as an embedded (rawExtention) object which cannot be directly validated. See: https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#rawextension Signed-off-by: Yu Qi Zhang <jerzhang@redhat.com>
f973a16
to
f473d5d
Compare
Updated comment for more context |
Content didn't change /lgtm Will defer to @kikisdeliveryservice to remove hold |
thank you, @yuqi-zhang ! /hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ashcrow, runcom, yuqi-zhang 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 |
/test unit |
/retest |
1 similar comment
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
uhm /retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/test e2e-gcp-upgrade |
/retest |
lgtm, thanks! |
@yuqi-zhang: All pull requests linked via external trackers have merged. Bugzilla bug 1809274 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. |
@yuqi-zhang: new pull request created: #1531 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. |
PR openshift#1524 introduced kubeletconfig as an embedded resource: x-kubernetes-embedded-resource: true This validates our config against the upstream config which differs in the placement of api version and kind. The result is that our kubeletconfigs are no longer valid and are unable to be applied. This PR removes the check and unbreaks our kubeletconfigs.
PR openshift#1524 introduced kubeletconfig as an embedded resource: x-kubernetes-embedded-resource: true This validates our config against the upstream config which differs in the placement of api version and kind. The result is that our kubeletconfigs are no longer valid and are unable to be applied. This PR removes the check and unbreaks our kubeletconfigs.
Hi, |
The kubelet config is now validated, but fields are being silently
dropped since its an "unknown field" (rawExtension), which by
default is pruned by the validator.
Signed-off-by: Yu Qi Zhang jerzhang@redhat.com