operator: apply crd.yaml Error
version 0.35.1 —update —> version 0.36.1
items:map[description:Volume represents a named volume in a pod that may be accessed by any container in the pod. required:[name] type:object x-kubernetes-preserve-unknown-fields:true] type:array]] type:object] status:map[description:Most recent observed status of the VMAlertmanager cluster. Operator API itself. More info: https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status properties:map[availableReplicas:map[description:AvailableReplicas Total number of available pods (ready for at least minReadySeconds) targeted by this VMAlertmanager cluster. format:int32 type:integer] paused:map[description:Paused Represents whether any actions on the underlaying managed objects are being performed. Only delete actions will be performed. type:boolean] replicas:map[description:ReplicaCount Total number of non-terminated pods targeted by this VMAlertmanager cluster (their labels match the selector). format:int32 type:integer] unavailableReplicas:map[description:UnavailableReplicas Total number of unavailable pods targeted by this VMAlertmanager cluster. format:int32 type:integer] updatedReplicas:map[description:UpdatedReplicas Total number of non-terminated pods targeted by this VMAlertmanager cluster that have the desired version spec. format:int32 type:integer]] required:[availableReplicas paused replicas unavailableReplicas updatedReplicas] type:object]] required:[spec] type:object]] served:true storage:true subresources:map[]]]]]": cannot convert int64 to float64
- kubectl delete CustomResourceDefinition vmalertmanagers.operator.victoriametrics.com
apply crd.yaml. is ok !
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (6 by maintainers)
I just tested it and didn’t have any issues. I’m unable to reproduce the error. If I come across it again somewhere else, I’ll come back and let you know.
@Haleygo could you please take a look?