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

## 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.

Reviewed-on: #166

This commit was merged in pull request #166.

This commit is contained in:

Ben Vincent

2026-05-25 22:44:24 +10:00

parent f403c6b05d

commit 6497dab25e

1 changed files with 0 additions and 1 deletions

									
										apps/base/puppet/service_puppetdb.yaml
									
		-1
	
												View File
												
					@@ -9,7 +9,6 @@ metadata:

					  name: puppetdb

					  name: puppetdb

					  namespace: puppet

					  namespace: puppet

					spec:

					spec:

					  clusterIP: null

					  ports:

					  ports:

					  - name: pdb-http

					  - name: pdb-http

					    port: 8080

					    port: 8080