Upgrade dependencies: go-client v8.0.0, k8s v1.11 #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is not well tested, but I did the annoying work to upgrade the kubernetes go-client dependency to version 8.0.0 and adjust to the breaking changes that comes with it (mostly breaking changes that were introduced by version 5.0.0). Also I upgraded the kubernetes object's apiVersion where applicable.
I did not test it thouroughly. There seem to be bugs, but since I started using kube-prompt just today, I don't even know yet, if these bugs are related to the upgrade. But I suppose this PR is still worthwhile to move towards an up to date kubernetes client.
Add dependency to apimachinery; use it for ListOptions
Change code to reflect breaking changes of go-client v5.0.0:
clientsets to avoid ambiguity.
See https://github.com/kubernetes/client-go/blob/master/CHANGELOG.md#v500
Rename package imports that have API version as their last label to
better reflect which API they represent
Migrate objects to newer API versions: Some k8s objects have migrated
to newer apiVersions like apps/v1, core/v1.