Remove priority field from the APIService manifest to make it compatible with 1.11+ bootstrap clusters #486
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.
What this PR does / why we need it:
As of Kubernetes 1.11, the
priority
field has been removed from the APIService resource. Thepriority
field have been replaced withgroupPriority
andversionPriority
fields.More about those fields can be found in godoc comments.
Those fields have been backported to older Kubernetes versions, including 1.10 used by Minikube. Here's a commit that introduced that change: kubernetes/kubernetes@d13ad28
Trying to create a cluster using
clusterctl
with a bootstrap cluster version 1.11 or newer, results in the following error:After the fix is in place, this part passes without any other problem. We already have both
versionPriority
andgroupPriority
, so I believe we don't need any other change.I have tested with both external cluster version 1.11, 1.12 (current master), 1.10, and Minikube 1.10.
Release note: