As of now, there is no way to know the Operator version linked to the CRD present in etcd.Some of the ways to identify it are to know the fields modified and validate it manually. As the version of API remains the same and only fields get added, It helps user to have a way to identify the operator version linked to it.
Some of the possibilities to embed operator version are as follows
spec
status
Annotations
Labels.
End result of this is to run a command like kubectl get crd perconaservermongodbs.psmdb.percona.com --<options> and get operator version.
I believe OLM adds labels for the CRD, this also needs to be taken care of as Everest uses OLM.
As of now, there is no way to know the Operator version linked to the CRD present in etcd.Some of the ways to identify it are to know the fields modified and validate it manually. As the version of API remains the same and only fields get added, It helps user to have a way to identify the operator version linked to it.
Some of the possibilities to embed operator version are as follows
spec
status
Annotations
Labels.
End result of this is to run a command like
kubectl get crd perconaservermongodbs.psmdb.percona.com --<options>and get operator version.I believe OLM adds labels for the CRD, this also needs to be taken care of as Everest uses OLM.
FYI @Diogo Recharte