-
Notifications
You must be signed in to change notification settings - Fork 731
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Init Openshift documentation #1315
Conversation
Co-Authored-By: Peter Brachwitz <peter.brachwitz@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to identify which portions of this document are relevant when installing on OpenShift via OLM?
Also, is there a way to avoid the elastic-system namespace and co-locate the global and namespace roles/operator in each namespace with the goal being to rollout operator upgrades in a controlled fashion, one namespace at a time. The global role/operator seems to make that difficult.
Co-Authored-By: Anya Sabo <1638148+anyasabo@users.noreply.github.com>
docs/openshift.asciidoc
Outdated
oc new-project elastic # creates the elastic project | ||
---- | ||
+ | ||
By default the operator will watch and create resources in the `default` namespace. You need to patch the operator to manage resources in an other namespace. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be worth providing an example of listening cluster wide here as well, since I imagine that is a common use case
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would be tempted to say that it is not specific to Openshift, so it should be documented elsewhere. That said it's an interesting point, I'm not sure we have a document explaining how to do that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah that's a good point. We should definitely add that to a larger configuration doc and perhaps link to it from here
Would it be worthwhile to document the APM limitations in this doc as well? |
It will not run, the Docker image is not compatible with restricted environments like Openshift: elastic/beats#12905 I will add a note in the APM documentation (I'm working on it) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor rewording.
This was nice work! Just some minor nits and suggest adding a section on running a cluster wide operator |
Co-Authored-By: Anya Sabo <1638148+anyasabo@users.noreply.github.com>
Thank you all for your great feedback ! ❤️ |
Just noticed two minor nits that could take or leave, either way 🥇 |
Good point, I will address it in an other PR. |
This PR adds some documentation for Openshift (mostly for running the quickstart on it)