Update readme to cover OLM way of installing the operator
Closed this issue · 2 comments
Well over a year ago I integrated with Operator Lifecycle Management, which changed from manually running a bunch of yaml to instead adding my catalog source and subscription to get the operator installed. I covered that in chapter 9 of my MicroProfile book (https://www.amazon.com/Practical-Cloud-Native-Java-Development-MicroProfile/dp/1801078807), and in a Medium article (https://medium.com/hybrid-cloud-engineering/portability-of-applications-across-kubernetes-distributions-part-1-9b8a5eae4890), but need to update the README.md file in this repo to say that too.
Let's document the operator-sdk run bundle approach in the readme. That's more straightforward than all of the CatalogSource stuff, which is mostly for integrating into OperatorHub stuff in the fancy OpenShift console, which we mostly don't use these days (focusing on EKS or AKS instead).
I merged the PR from Celina yesterday