(DOCSP-13959): cross-namespace deployment docs #319
Conversation
jeff-allen-mongo
left a comment
jeff-allen-mongo
left a comment
There was a problem hiding this comment.
Some of the links don't seem to work. Content looks solid though.
jeff-allen-mongo
left a comment
jeff-allen-mongo
left a comment
There was a problem hiding this comment.
LGTM with one non-blocking comment.
| - mongodb-kubernetes-operator | ||
| imagePullPolicy: Always | ||
| env: | ||
| - name: WATCH_NAMESPACE |
There was a problem hiding this comment.
Can you highlight lines in markup? Might be helpful here if so, but definitely not necessary.
There was a problem hiding this comment.
I don't think there's a simple way to do this. I did a little research but came up empty.
docs/install-upgrade.md
Outdated
|
|
||
| ### Understand Deployment Scopes | ||
|
|
||
| You can deploy the MongoDB Community Kubernetes Operator with different scopes based on where you want to deploy Ops Manager and MongoDB Kubernetes resources: |
There was a problem hiding this comment.
The Community Operator doesn't support Ops Manager :)
There was a problem hiding this comment.
oof. copy / paste mistake from the enterprise operator. fixed.
alyacb
left a comment
alyacb
left a comment
There was a problem hiding this comment.
Looks good, but the reference to Ops Manager should be removed before merging.
jwilliams-mongo
force-pushed
the
DOCSP-13959
branch
from
1ede7a6 to
62d31bd
Compare
4 participants
All Submissions:
closes #XXXXin your comment to auto-close the issue that your PR fixes (if such).closes #316
JIRA