You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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
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 forportworx-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:
uname -a
):The text was updated successfully, but these errors were encountered: