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

Fix Gateway API CRDs #3065

Merged
merged 3 commits into from
Oct 9, 2023
Merged

Fix Gateway API CRDs #3065

merged 3 commits into from
Oct 9, 2023

Conversation

t-eckert
Copy link
Contributor

@t-eckert t-eckert commented Oct 9, 2023

It looks like the copywrite CLI deleted the Gateway CRDs we install. This would have broken us if it was released. I regenerated the external CRDs and added them to the Copywrite ignore given they are just pulled in from the Gateway SIG anyway and are not our IP.

Changes proposed in this PR:

  • Regenerate external Gateway CRDs
  • Remove errant .yml
  • Add external CRDs to copywrite ignore

@t-eckert t-eckert added the pr/no-changelog PR does not need a corresponding .changelog entry label Oct 9, 2023
@david-yu
Copy link
Contributor

david-yu commented Oct 9, 2023

Thanks does this need to be backported?

@t-eckert
Copy link
Contributor Author

t-eckert commented Oct 9, 2023

Thanks does this need to be backported?

I was just looking at that. The regression did not get into 1.2.x so we are fine there. I don't see a release branch cut for 1.3.x yet so I don't think it needs backporting.

@t-eckert t-eckert added the pr/no-backport signals that a PR will not contain a backport label label Oct 9, 2023
Copy link
Member

@nathancoleman nathancoleman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad you found this!

@t-eckert t-eckert merged commit e937e6d into main Oct 9, 2023
50 of 55 checks passed
@t-eckert t-eckert deleted the fix-external-crds branch October 9, 2023 20:35
@nathancoleman
Copy link
Member

@t-eckert it looks like there's a release/1.3.0-rc1 branch as of a couple hours ago that we probably want to port this into

@NicoletaPopoviciu
Copy link
Contributor

@curtbushko FYI

@t-eckert
Copy link
Contributor Author

t-eckert commented Oct 9, 2023

Lol, timing issue. I will do a manual backport.

@t-eckert
Copy link
Contributor Author

t-eckert commented Oct 9, 2023

Oh, I guess I was looking for 1.3.x not 1.3.0-rc1. Don't we normally have that first branch and branch into the latter?

t-eckert pushed a commit that referenced this pull request Oct 9, 2023
* Regenerate external Gateway CRDs

* Remove errant .yml

* Add external CRDs to copywrite ignore
@t-eckert
Copy link
Contributor Author

t-eckert commented Oct 9, 2023

Created #3066

t-eckert pushed a commit that referenced this pull request Oct 10, 2023
Fix Gateway API CRDs (#3065)

* Regenerate external Gateway CRDs

* Remove errant .yml

* Add external CRDs to copywrite ignore
@nathancoleman
Copy link
Member

It looks to me like the copyright headers did make it into 1.2.0, 1.2.1 and 1.2.2. Based on this, I'm going to backport to release/1.2.x.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.2.x This release branch is no longer active. pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants