Skip to content
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

Documentation should include guidance on when to use -namespace flag #213

Open
SQUIDwarrior opened this issue Apr 30, 2020 · 0 comments
Open
Assignees

Comments

@SQUIDwarrior
Copy link

The documentation should explain how to use the -namespace flag, and when to use it.

  • What version of the operator are you running?
    0.6.0

  • What version of Kubernetes are you running? Please include the output of kubectl version.
    1.15

  • What are you trying to do?
    Deploy m3db-operator to a large Kubernetes cluster

  • What did you expect to happen?
    That it would deploy normally.

  • What happened?
    With very large clusters, the M3DB nodes would timeout waiting for their pod identity. This is because the m3db-operator is listening for all pod events by default, and it cannot keep up. When this happens, the pod identity annotation is not applied to the M3DB pods before they timeout and restart, causing the cluster to never fully boot. This is fixed by using the -namespace flag on the m3db-operator container to filter the events to just the namespace where the M3DB pods are running, but no where in the documentation does it explain that this flag exists, or when to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants