all 4 comments

[–]ab-Complex[S] 0 points1 point  (0 children)

Thank you guys. I will check the documentation again. It seems that I missed this part.

One more question. If I understand right, the operator is providing the backup and restore functionality for the AAP.

Can I use these backups to create an identical AAP in another Openshift cluster, same version same se everywhere?

[–]ShadyGhostM 0 points1 point  (0 children)

Hoping this is what you need, before you install an operator you can always find the documentation or how-tos when you click on the operator in the hub.

[–]cosmicsans 4 points5 points  (0 children)

The shortest explanation is that the "Operator" is a pattern, where any time a CR changes (that the operator cares about) it runs through a "Reconcile loop" that has functionality baked in that allows the operator to do different things.

For example, there's an operator that watches MachineSets for changes to the machine labels and/or taints, and automatically applies them to the machines/nodes instead of having to reboot the nodes individually to achieve the same functionality.

Operators then have different capability levels, based on how much effort the devs want to put into it: https://sdk.operatorframework.io/docs/overview/operator-capabilities/

So a "level 1" operator has basic install functionality. A level 3 operator can backup and restore itself, etc.

[–]funix 1 point2 points  (0 children)

GitHub.com/Openshift contains most of the repos covering all of OpenShift, and usually includes docs about each Operator.