Skip to content
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

Merged
merged 2 commits into from
Aug 12, 2020

Conversation

ashish-amarnath
Copy link
Member

@ashish-amarnath ashish-amarnath commented Aug 12, 2020

Signed-off-by: Ashish Amarnath ashisham@vmware.com

Fixes #2811

@github-actions github-actions bot requested a review from nrb August 12, 2020 02:50
@ashish-amarnath ashish-amarnath added this to the v1.5 milestone Aug 12, 2020
@carlisia
Copy link
Contributor

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.

@nrb
Copy link
Contributor

nrb commented Aug 12, 2020

@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.

@ashish-amarnath
Copy link
Member Author

I was able to get this to work with a more elegant hack.
@nrb and @carlisia PTAL

@nrb nrb removed the On Hold label Aug 12, 2020
@carlisia
Copy link
Contributor

carlisia commented Aug 12, 2020

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.

@ashish-amarnath ashish-amarnath changed the title [WIP] 🐛 Manually patch the generated yaml for restore CRD as a hacky workaround 🐛 Manually patch the generated yaml for restore CRD as a hacky workaround Aug 12, 2020
Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
Signed-off-by: Ashish Amarnath <ashisham@vmware.com>
@ashish-amarnath
Copy link
Member Author

@carlisia added some context to the update-generated-crd-code.sh file

Copy link
Contributor

@carlisia carlisia left a 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!

@ashish-amarnath ashish-amarnath changed the title 🐛 Manually patch the generated yaml for restore CRD as a hacky workaround 🐛 Patch generated yaml for restore CRD as a hacky workaround Aug 12, 2020
@nrb nrb merged commit d4bbd7b into vmware-tanzu:main Aug 12, 2020
@ashish-amarnath ashish-amarnath deleted the k8s-1-18-crd-hack branch August 19, 2020 20:57
georgettica pushed a commit to georgettica/velero that referenced this pull request Dec 23, 2020
…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>
georgettica pushed a commit to georgettica/velero that referenced this pull request Jan 26, 2021
…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>
vadasambar pushed a commit to vadasambar/velero that referenced this pull request Feb 3, 2021
…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>
dharmab pushed a commit to dharmab/velero that referenced this pull request May 25, 2021
…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>
ywk253100 pushed a commit to ywk253100/velero that referenced this pull request Jun 29, 2021
…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>
gyaozhou pushed a commit to gyaozhou/velero-read that referenced this pull request May 14, 2022
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 Velero CRDs from the main branch cannot be installed on a kubernetes 1.18 cluster
3 participants