kubernetes-sigs/cluster-api-provider-vsphere

Improve handling of unreachable vCenter

Open

#1,443 opened on Feb 17, 2022

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Go (320 forks)auto 404
area/govmomihelp wantedkind/featurelifecycle/frozen

Repository metrics

Stars
 (417 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

Describe the solution you'd like Currently if i have an vCenter that CAPV cant reach it slows down the reconciliation for all resources, as it will retry reaching the offending vCenter every reconciliation loop. It would be nice to move unreachable resources into a separate back off (ideally with a ceiling) so that they dont block reconciliation of still reachable resources

Contributor guide

Research direction
Investigate the current reconciliation logic for vCenter connectivity. Identify where and how retries are implemented. Propose a separate backoff mechanism (e.g., exponential backoff with a ceiling) for unreachable vCenters, ensuring it does not block reconciliation of reachable resources. Check existing controller patterns in CAPV for rate limiting or retry queues.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65