fix(puppet): remove explicit clusterIP: null from puppetdb Service #166

Merged
unkinben merged 1 commits from benvin/puppet-outsync-fix into main 2026-05-25 22:44:25 +10:00
Owner

Summary

  • Removes clusterIP: null from the puppetdb Service spec

Why

Setting clusterIP: null makes ArgoCD's desired state explicit about the field being null. Kubernetes assigns a real IP on creation and the field is immutable afterward. The null vs assigned-IP mismatch causes permanent OutOfSync on the puppetdb Service. Removing the field means ArgoCD no longer claims ownership of clusterIP, so the API server's value is authoritative.

## Summary - Removes `clusterIP: null` from the `puppetdb` Service spec ## Why Setting `clusterIP: null` makes ArgoCD's desired state explicit about the field being null. Kubernetes assigns a real IP on creation and the field is immutable afterward. The null vs assigned-IP mismatch causes permanent OutOfSync on the puppetdb Service. Removing the field means ArgoCD no longer claims ownership of `clusterIP`, so the API server's value is authoritative.
unkinben added 1 commit 2026-05-24 23:50:01 +10:00
fix(puppet): remove explicit clusterIP: null from puppetdb Service
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
d2443c9681
Setting clusterIP: null means ArgoCD's desired state has null but the
live cluster assigns a real IP on creation. This causes permanent
OutOfSync as the two values never match. Removing the field lets the
API server own it without ArgoCD competing.
unkinben merged commit 6497dab25e into main 2026-05-25 22:44:25 +10:00
unkinben deleted branch benvin/puppet-outsync-fix 2026-05-25 22:44:25 +10:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#166