fix(kubernetes): temporary solution for updated k8s python client
This commit is contained in:
parent
07d6fe7442
commit
977b5bca85
1477 changed files with 422337 additions and 1 deletions
18
kubernetes/base/leaderelection/README.md
Normal file
18
kubernetes/base/leaderelection/README.md
Normal file
|
@ -0,0 +1,18 @@
|
|||
## Leader Election Example
|
||||
This example demonstrates how to use the leader election library.
|
||||
|
||||
## Running
|
||||
Run the following command in multiple separate terminals preferably an odd number.
|
||||
Each running process uses a unique identifier displayed when it starts to run.
|
||||
|
||||
- When a program runs, if a lock object already exists with the specified name,
|
||||
all candidates will start as followers.
|
||||
- If a lock object does not exist with the specified name then whichever candidate
|
||||
creates a lock object first will become the leader and the rest will be followers.
|
||||
- The user will be prompted about the status of the candidates and transitions.
|
||||
|
||||
### Command to run
|
||||
```python example.py```
|
||||
|
||||
Now kill the existing leader. You will see from the terminal outputs that one of the
|
||||
remaining running processes will be elected as the new leader.
|
Reference in a new issue