You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The status of the crd/missioncontrolclusters.missioncontrol.datastax.com object indeed shows the presence of both v1beta1 and v1beta2 in its status as storedVersions:
status:
acceptedNames:
kind: MissionControlCluster
listKind: MissionControlClusterList
plural: missioncontrolclusters
shortNames:
- mccluster
- mcclusters
singular: missioncontrolcluster
conditions:
- lastTransitionTime: "2024-02-12T18:15:57Z"
message: no conflicts found
reason: NoConflicts
status: "True"
type: NamesAccepted
- lastTransitionTime: "2024-02-12T18:16:02Z"
message: the initial names have been accepted
reason: InitialNamesAccepted
status: "True"
type: Established
storedVersions:
- v1beta1
- v1beta2
We need to figure out how to perform the upgrade and remove traces of v1beta1 in the CRD status.
┆Issue is synchronized with this Jira Bug by Unito
┆Reviewer: Alexander Dejanovski
┆Issue Number: K8CL-8
The text was updated successfully, but these errors were encountered:
While upgrading the ui-playground dataplane to the latest version, the CRD upgrader failed with the following message:
The status of the
crd/missioncontrolclusters.missioncontrol.datastax.com
object indeed shows the presence of both v1beta1 and v1beta2 in its status as storedVersions:We need to figure out how to perform the upgrade and remove traces of v1beta1 in the CRD status.
┆Issue is synchronized with this Jira Bug by Unito
┆Reviewer: Alexander Dejanovski
┆Issue Number: K8CL-8
The text was updated successfully, but these errors were encountered: