You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/10/15 11:04:00 UTC
[GitHub] [camel-k] astefanutti opened a new pull request #1765: fix: Correct operator leader election ConfigMap lock name
astefanutti opened a new pull request #1765:
URL: https://github.com/apache/camel-k/pull/1765
Fixes the discrepancy introduced with #1741.
**Release Note**
```release-note
NONE
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] heiko-braun commented on pull request #1765: fix: Correct operator leader election ConfigMap lock name
Posted by GitBox <gi...@apache.org>.
heiko-braun commented on pull request #1765:
URL: https://github.com/apache/camel-k/pull/1765#issuecomment-709215674
Out of curiosity, what do we need lesder election for? What leader election protocol does it use?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on pull request #1765: fix: Correct operator leader election ConfigMap lock name
Posted by GitBox <gi...@apache.org>.
astefanutti commented on pull request #1765:
URL: https://github.com/apache/camel-k/pull/1765#issuecomment-709254095
> Out of curiosity, what do we need leader election for? What leader election protocol does it use?
It is to make sure only one operator instance operates on the controlled custom resources. Technically, it is just a ConfigMap that materialises a lock.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti merged pull request #1765: fix: Correct operator leader election ConfigMap lock name
Posted by GitBox <gi...@apache.org>.
astefanutti merged pull request #1765:
URL: https://github.com/apache/camel-k/pull/1765
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-k] astefanutti commented on pull request #1765: fix: Correct operator leader election ConfigMap lock name
Posted by GitBox <gi...@apache.org>.
astefanutti commented on pull request #1765:
URL: https://github.com/apache/camel-k/pull/1765#issuecomment-709262731
Adding that, on a typical production environment, an operator deployment is likely to be scaled up to achieve high availability, leading to multiple instances, among which only one can actually operates on the custom resources.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org