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

Acquire leader lease via specific resource object instead of ConfigMap for the portworx-pvc-controller deployment #11

Closed
hr1sh1kesh opened this issue Feb 6, 2018 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@hr1sh1kesh
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
Leader election fails in some cases for the portworx-pvc-controller pods. The --leader-elect-resource-lock should be for a specific object created just for portworx-pvc-controller to work.

What you expected to happen:
leader election of the portworx-pvc-controller deployment to be successful all the time.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Container Orchestrator and version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@hr1sh1kesh hr1sh1kesh added the bug Something isn't working label Feb 6, 2018
@hr1sh1kesh hr1sh1kesh self-assigned this Feb 6, 2018
@hr1sh1kesh hr1sh1kesh changed the title Acquire leader lease via endpoints instead of ConfigMap for the portworx-pvc-controller deployment Acquire leader lease via specific resource object instead of ConfigMap for the portworx-pvc-controller deployment Feb 6, 2018
@hr1sh1kesh
Copy link
Contributor Author

Fixed in the latest stork deployment spec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant