Kuadrant / Kuadrant/dns-operator

POC Health checks that cause unpublishing of unhealthy endpoints

Open
#689 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
12
Forks
23
Avg merge
1d 4h
Merged PRs (30d)
14

Description

The first step here will likely be a spike / POC to see how this might function.

Early thoughts:
- Continue with the delete label and the stop labels as planned before
- Await visibility of label in zone before unpublishing (to avoid NXDomain)
- Process the unpublishing for healthchecks in a separate plan similar to the DNS Failover
- Only process unpublishing for healthchecks if no other changes occurred in this reconcile.
- HealthCheckProbe CRs created by kuadrant-operator
- Status of relevant DNSRecord updated from reconcile of HealthCheckProbeCR
- Some mechanism to avoid republishing unhealthy endpoints after unpublishing.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the HealthCheckProbe CRs created by kuadrant-operator, the DNSRecord reconciliation that updates status, and the existing DNS Failover plan. Define and validate a POC covering label visibility, separate health-check unpublishing, reconcile safeguards, and prevention of republishing unhealthy endpoints.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure, networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.