chore: separate spiffe/spire from k8s #1100

New issue

Closed

opened 2026-03-28 04:31:41 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:31:41 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #3006
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/3006
Original created: 2026-03-08T07:52:21Z

We need to switch the default k8s helm/manifest installation of ServiceRadar to be mTLS based and not include all of the spiffe/spire stuff. Making spiffe/spire a default requirement is not suitable for clusters where we may not have access to create cluster wide resources (CRDs). We don't need to rip-out support for spiffe/spire completely, but after this change it will be completely optional and the default helm/manifest installation will just generate mTLS certs for all the services that need them. We're already using mTLS-only docker compose deployments.

remove spiffe/spire from helm/k8s manifests
update values.yaml
update values-demo.yaml
update docs
cleanup demo k8s namespace

Imported from GitHub. Original GitHub issue: #3006 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/3006 Original created: 2026-03-08T07:52:21Z --- We need to switch the default k8s helm/manifest installation of ServiceRadar to be mTLS based and not include all of the spiffe/spire stuff. Making spiffe/spire a default requirement is not suitable for clusters where we may not have access to create cluster wide resources (CRDs). We don't need to rip-out support for spiffe/spire completely, but after this change it will be completely optional and the default helm/manifest installation will just generate mTLS certs for all the services that need them. We're already using mTLS-only docker compose deployments. - [x] remove spiffe/spire from helm/k8s manifests - [x] update values.yaml - [x] update values-demo.yaml - [x] update docs - [x] cleanup `demo` k8s namespace

Rows
Columns