-
Bug
-
Resolution: Done
-
Major
-
IDP 1.0 TP
-
False
-
None
-
False
Since IDP is supported from ACM 2.4+, is it possible to change our placements to v1beta1 so that it doesn't negatively effect other placements in ACM in 2.5+ but still work in 2.4.z? Or have it so that we can create CRDs with either version?
New features in ACM 2.5 / MCE 2.0 such as Placement Tolerations require v1beta1 in order to work, and as such v1alpha1 has been deprecated after 2.4. IDP however still uses v1alpha1, and our placements are auto-updating other placements with this version:
% oc get placement placement2 -o yaml
apiVersion: cluster.open-cluster-management.io/v1beta1
kind: Placement
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"cluster.open-cluster-management.io/v1beta1","kind":"Placement","metadata":{"annotations":{},"name":"placement2","namespace":"default"},"spec":{"tolerations":[{"operator":"Exists"}]}}
creationTimestamp: "2022-05-23T08:50:19Z"
finalizers:
- authrealm.identitatem.io/cleanup
generation: 8
managedFields:
- apiVersion: cluster.open-cluster-management.io/v1beta1
fieldsType: FieldsV1
fieldsV1:
f:status:
.: {}
f:conditions: {}
f:numberOfSelectedClusters: {}
manager: Go-http-client
operation: Update
subresource: status
time: "2022-05-23T08:50:19Z"
- apiVersion: cluster.open-cluster-management.io/v1alpha1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:finalizers:
.: {}
v:"authrealm.identitatem.io/cleanup": {}
f:spec:
f:prioritizerPolicy:
.: {}
f:mode: {}
manager: idp-mgmt
operation: Update
time: "2022-05-23T08:50:19Z"
- apiVersion: cluster.open-cluster-management.io/v1alpha1
fieldsType: FieldsV1
fieldsV1:
f:spec: {}
manager: oc
operation: Update
time: "2022-05-23T08:50:19Z"
- apiVersion: cluster.open-cluster-management.io/v1alpha1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations: {}
manager: kubectl-client-side-apply
operation: Update
time: "2022-05-23T09:07:27Z"
- apiVersion: cluster.open-cluster-management.io/v1beta1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:kubectl.kubernetes.io/last-applied-configuration: {}
manager: kubectl-client-side-apply
operation: Update
time: "2022-05-23T09:08:26Z"
name: placement2
namespace: default
resourceVersion: "133836751"
uid: 62fae404-2625-4c1e-8cf5-070c8151dd46
spec:
prioritizerPolicy:
mode: Additive
status:
conditions:
- lastTransitionTime: "2022-05-23T08:50:19Z"
message: No ManagedCluster matches any of the cluster predicate
reason: NoManagedClusterMatched
status: "False"
type: PlacementSatisfied
numberOfSelectedClusters: 0
Cluster Details
- Operator Snapshot Version
- ACM 2.5RC4
- MCE 2.0RC
- OpenShift Container Platform
- 4.10.13