k8s 1.28 (edge 1.16)

[nfuden]

Version

None

Is your feature request related to a problem? Please describe.

Part of maintaining a solid product and avoiding breaking changes or massive backports over the life of an LTS branch we must keep our deps in check. In this case its kubernetes

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional Context

No response

[sam-heilbron]

solo-io#8164 (comment)

[sam-heilbron]

https://github.com/solo-io/skv2/blob/main/go.mod#L3

[nfuden]

@Sodman we are looking at picking this soon lets chat

[Sodman]

No issues from a GP perspective with bumping skv2. GME repo is already on k8s 1.28 dependencies, so I recommend we just bump the minor version of skv2 release and hold off on the next "major" bump until 1.29.

[sheidkamp]

Documents from the 1.27 update that may be of use:

solo-projects PR that references all of the other PRs: https://github.com/solo-io/solo-projects/pull/5200
google doc for tracking the repositories and their statuses (mostly the same information as the PR): https://docs.google.com/document/d/10JJDpwPzssSBDlj2B_eTisqZqtoHZPqdt-jmQyrneKU

[davidjumani]

Breaking changes :

• Unaffected : Changed kubectl version default output to be identical to what kubectl version --short printed
• Unaffected: Deprecated support for CSI migration of Ceph RBD volumes.
• Unaffected: The deprecated flag --lock-object-namespace and --lock-object-name have been removed from kube-scheduler
• Unaffected: KMSv1 is deprecated and will only receive security updates going forward
• Affected: codegen - Deprecate generate*groups.sh -> kube_codegen.sh. We can not use this new script yet as kube_codegen.sh only works when the repo is in the sigs.k8s folder. Ref: Support code generation via kube_codegen.sh when the repository path is outside the package name kubernetes/code-generator#165

Other changes :

• Helm upgrade to v3.13.2 - Bumped to support v1.28
  
• Moby upgrade to v24.0.7+incompatible - With the helm upgrade, the docker libs were bumped as well. Bumped moby to the corresponding version

Affected repos :

• cloud-builders - https://github.com/solo-io/cloud-builders/pull/118 - released v0.8.0
• go-utils - chore: bump k8s to 1.28 solo-io/go-utils#523 - released v0.24.8
• k8s-utils - chore: bump k8s to 1.28 solo-io/k8s-utils#44 - released v0.6.0
  - k8s bump
  - go-utils bump
• solo-kit - chore: bump k8s to 1.28 solo-io/solo-kit#548 - released v0.34.0
  - k8s bump
  - go-utils bump
  - k8s-utils
  - code-generator script changes
• skv2 - chore: bump k8s to 1.28 solo-io/skv2#518 - released v0.36.0
  - k8s bump + corresponding minor code changes
• rate-limiter - https://github.com/solo-io/rate-limiter/pull/193 (did not bump solo repo dependencies), https://github.com/solo-io/rate-limiter/pull/214 - released v0.11.4
• solo-apis (gloo-repo-branch used by gloo) - Solo APIs. @tag-name=sa-k8s-1.28-bump solo-io/solo-apis#1084 - created tag sa-k8s-1.28-bump
  - k8s bump
• gloo - [Migrated] chore: bump k8s to 1.28 solo-io/gloo#8928 - released v1.16.0-beta28
  - k8s bump
  - go-utils bump
  - k8s-utils bump
  - skv2 bump
  - solo-apis bump
  - solo-kit bump
• solo-apis (gloo-main used by solo-projects) - Sync APIs. @tag-name=gloo-v1.16.0-beta28 solo-io/solo-apis#1089
  - add the changes to the PR generated by gloo release, before merging it
• caching-service - https://github.com/solo-io/caching-service/pull/26 - released v0.6.0
• external-apis - Bump k8s to 1.28 solo-io/external-apis#38 - released gloo-v0.2.1
• ext-auth-service - https://github.com/solo-io/ext-auth-service/pull/681 - released v0.55.0
• solo-projects - https://github.com/solo-io/solo-projects/pull/5529