Created
May 2, 2019 14:32
-
-
Save richm/c3ba9bfe8ab7f486d49ccfa32569877b to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After moving the elasticsearch-operator to the namespace openshift-operators-redhat, the elasticsearch-operator deployment is not created in that namespace. Steps: https://github.com/richm/origin-aggregated-logging/commit/2b2a57ba7dc7c19a8466d327fc92120302018814 | |
Create namespace openshift-operators-redhat | |
Create operatorgroup openshift-operators-redhat in that namespace with targetNamespace openshift-logging | |
Create namespace openshift-logging | |
Create operatorgroup openshift-logging in that namespace with targetNamespace openshift-logging | |
Create catalogsourceconfig for elasticsearch | |
Create catalogsourceconfig for clusterlogging | |
Create subscription for elasticsearch | |
Create subscription for clusterlogging | |
Wait for the elasticsearch-operator pod to be running in openshift-operators-redhat and cluster-logging-operator to be running in openshift-logging | |
I never see the elasticsearch-operator Deployment created in openshift-operators-redhat - this used to work when using openshift-operators |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment