Bump kubevirt to v1.1.0, k8s to v1.26.10, Harvester to v1.3.0 #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.
Solve issue: harvester/harvester#5137, in Harvester v1.3.0, the
load-balancer-harvester
cannot handle vmi correctly (client still use v0.5.4), causes the feature is partially broken.Note:
In v1.3.0, when a VM is created, and there is no LB related configuration, the LB pod still flood such log
With this PR, such log is gone, and the VM is correctly added a
wrangler.cattle.io/harvester-lb-vmi-controller
finalizer.Other bug fix is not related to this PR, and will be further on top of this PR in future.
PR harvester/harvester#4787 is referred to bump all those dependencies.
Todo: After this PR is merged, we need to release a new version and update the chart.
BTW:
also note issue
kubernetes/kube-openapi#404
and the solution:
prometheus-operator/prometheus-operator#5667 (comment)
In harvester and load-balancer-harvester, the used openapi version is:
k8s.io/kube-openapi => k8s.io/kube-openapi v0.0.0-20230308215209-15aac26d736a