Update gnostic dependency with gnostic-models

[liangyuanpeng]

Related:

• [Umbrella Issue] Replace google/gnostic import with google/gnostic-models kubernetes/kubernetes#118340

This PR changed:

• update go version to 1.20
• bump k8s.io packages to v0.28.4
• bump sigs.k8s.io/kustomize to v5.2.1
• bump sigs.k8s.io/controller-runtime to v0.16.3
• bump sigs.k8s.io/yaml to v1.4.0
• migrate from google/gnostic to google/gnostic-models

[k8s-ci-robot]

Welcome @liangyuanpeng!

It looks like this is your first PR to kubernetes-sigs/cli-utils 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cli-utils has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @liangyuanpeng. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[liangyuanpeng]

Now, i just use v0.28.0-alpha.4 to fix it, and i think we need to waiting for a stable version.

[liangyuanpeng]

Some api have changed, need update.

[liangyuanpeng]

cc @seans3 @Liujingfang1 @mortent @karlkfi

[stefanprodan]

@liangyuanpeng could you please revive this PR. We really need this merged to unblock the Flux upgrade to Kubernetes 1.28. Thank you!

[ash2k]

/ok-to-test

[ash2k]

/lgtm

@seans3 PTAL.

[seans3]

/lgtm

I believe you can even update to the latest v0.28.4 (instead of v0.28.0) if you prefer.

@karlkfi Is this update OK with you?

[liangyuanpeng]

@ash2k @seans3 Update to v0.28.4 and not v0.28.0, PTAL,Thanks!

[ash2k]

/lgtm

[stefanprodan]

To match Kubernetes 1.28 these could also be bumped:

	sigs.k8s.io/controller-runtime v0.16.3
	sigs.k8s.io/kustomize/kyaml v0.15.0
	sigs.k8s.io/yaml v1.4.0

For reference https://github.com/fluxcd/cli-utils/pull/1/files

[liangyuanpeng]

@stefanprodan Thanks for remind.
You are the end user and have already applied this change to fluxcd, so I followed your advice and updated. Since the CI is green without this change, it would be great if you could provide more information to increase the reviewer's confidence.

Sorry about duplicate lgtm.

[stefanprodan]

LGTM

Thanks @liangyuanpeng

[ash2k]

/lgtm

[ash2k]

@seans3 @karlkfi I think this is ready for merging, PTAL.

[mortent]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liangyuanpeng, mortent, stefanprodan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mortent]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[liangyuanpeng]

Thanks @mortent for approve and thanks @ash2k help to push it.