-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
🐛 Patch generated yaml for restore CRD as a hacky workaround #2814
Conversation
I think what's happening is that since "TCP" is the default, it should not be explicitly set, since it is implied. I looked at some other fields that have default values and they were not explicitly set. |
9643f28
to
e428841
Compare
@carlisia Per kubernetes/kubernetes#91395, though, if it's not set, there's another error. This seems to be confirming the second case mentioned in 91395. |
Cool. Would you mind please adding more context as documentation on hack/update-generated-crd-code.sh? Ideally the link to the issue would be used for reference if needed, but we wouldn't have to read the issue to figure out why we have this hack. What I'd like to see, is there a condition that would allow us to remove this script, what we would have to be on the lookout that would require extending that script if any, anything like that. |
Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
e428841
to
2579d95
Compare
@carlisia added some context to the |
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.
Thank you for digging into this!
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
…tanzu#2814) * 🐛 Patch generated yaml for restore CRD as a hacky workaround Signed-off-by: Ashish Amarnath <ashisham@vmware.com> * changelog Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
Signed-off-by: Ashish Amarnath ashisham@vmware.com
Fixes #2811