Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Update Kubernetes Go client to v0.21.3 (latest) #3515

Closed
wants to merge 3 commits into from

Conversation

kingdonb
Copy link
Member

@kingdonb kingdonb commented Jul 27, 2021

There remained some pins in the go.mod, which I required a release of helm-operator to be published (v1.4.0) in order to progress.

I've removed those pins and resolved all of the compile errors. We should be able to trivially bump the k8s-cli go version to 1.22.0 after merging this.

@kingdonb kingdonb changed the title Update Kubernetes Go client to v0.22.3 (latest) Update Kubernetes Go client to v0.21.3 (latest) Jul 27, 2021
@kingdonb kingdonb force-pushed the update-kubernetes-go-client branch from 673af36 to 63b9468 Compare July 27, 2021 20:06
@kingdonb kingdonb force-pushed the update-kubernetes-go-client branch from fd4c067 to e4e7f55 Compare July 27, 2021 21:57
@kingdonb kingdonb added this to the 1.24.0 milestone Jul 27, 2021
@kingdonb kingdonb force-pushed the update-kubernetes-go-client branch from e4e7f55 to 5ebf42c Compare August 4, 2021 21:29
@kingdonb kingdonb marked this pull request as ready for review August 17, 2021 12:46
@kingdonb kingdonb mentioned this pull request Aug 17, 2021
@kingdonb kingdonb mentioned this pull request Aug 17, 2021
Kingdon Barrett added 3 commits August 17, 2021 09:12
Signed-off-by: Kingdon Barrett <kingdon@weave.works>
* go mod download (go.sum)
* go mod updates for helm-operator package
* go mod download (helm-operator)

Signed-off-by: Kingdon Barrett <kingdon@weave.works>
* remove "replace" statement for go-autorest

With SOPS upgraded, "go mod tidy" now fails until this is removed.

* Resolve client-go issue from upgrade to 1.20

kubernetes/client-go#914 (comment)

* register deployments type

Signed-off-by: Kingdon Barrett <kingdon@weave.works>
@kingdonb
Copy link
Member Author

kingdonb commented Aug 17, 2021

This will conflict with #3512 , I will make them both as drafts PRs now and probably have to resolve them in a separate PR.

@kingdonb
Copy link
Member Author

Closed in favor of #3537

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant