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

Solo APIs. @tag-name=sa-k8s-1.28-bump #1084

Merged
merged 10 commits into from
Dec 6, 2023
Merged

Conversation

davidjumani
Copy link

@davidjumani davidjumani commented Nov 28, 2023

Bump to k8s 1.28
Updates the latest rate-limit protos as of 2023-12-05
Updates skv2 and adds the corresponding flags to mitigate breaking changes

@davidjumani davidjumani added the work in progress This pr is still being worked on label Nov 28, 2023
@davidjumani davidjumani changed the base branch from gloo-main to gloo-repo-branch November 28, 2023 23:27
@davidjumani davidjumani changed the title [WIP] chore: Bump k8s 128 chore: Bump k8s 128 Dec 5, 2023
@davidjumani davidjumani removed the work in progress This pr is still being worked on label Dec 5, 2023
@davidjumani davidjumani changed the title chore: Bump k8s 128 Solo APIs. @tag-name=sa-k8s-1.28-bump Dec 5, 2023
@davidjumani davidjumani added the work in progress This pr is still being worked on label Dec 5, 2023
storage: true

---
apiVersion: apiextensions.k8s.io/v1beta1
Copy link
Contributor

Choose a reason for hiding this comment

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

note to future reviewers: we don't care about the deletion of the failoverscheme crd because gloo (the only user of the gloo-repo-branch branch) doesn't reference the crds from solo-apis

@davidjumani davidjumani removed the work in progress This pr is still being worked on label Dec 6, 2023
@soloio-bulldozer soloio-bulldozer bot merged commit d2e3ed6 into gloo-repo-branch Dec 6, 2023
@soloio-bulldozer soloio-bulldozer bot deleted the bump-k8s-128 branch December 6, 2023 14:25
@sam-heilbron
Copy link
Collaborator

Given the conversations we had around why this branch exists, and what alternatives we considered, I think it would be helpful if we persisted those findings somewhere for future developers to discover. I could see value in any of the following places:

  • Add a README to this branch in solo-apis
  • Create an issue that outlines the technical debt of this solution, and add it as a comment in the go.mod above the dependency in gloo
  • Add an entry to the gloo oss or enterprise devel/ folder
  • Some other better option I'm not thinking of

@davidjumani
Copy link
Author

Added docs around this branch
#1090

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.

3 participants