python icon indicating copy to clipboard operation
python copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-client

add support Lease-based leader election (rather than ConfigMaps)

Open thesuperzapper opened this issue 3 years ago • 12 comments
trafficstars

What is the feature and why do you need it:

Currently, the K8S Python API only supports leader election using ConfigMapLock.

The K8S Go API supports using the proper Lease resource type with its LeaseLock, and actually recently removed support for the legacy ConfigMap approach.

We should update the Kubernetes Python API to provide a Lease-based leader election.

/cc @Invictus17 @tdihp

thesuperzapper avatar Aug 12 '22 06:08 thesuperzapper

/help

roycaihw avatar Aug 15 '22 16:08 roycaihw

@roycaihw: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Aug 15 '22 16:08 k8s-ci-robot

Hi,

I am beginner to Kuberenetes repo. Do you think this is a good issue to pick?

Jagrutiti avatar Aug 21 '22 16:08 Jagrutiti

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Feb 08 '23 00:02 k8s-triage-robot

/remove-lifecycle stale

thesuperzapper avatar Feb 08 '23 21:02 thesuperzapper