Skip to content

feat(service-profile): add service-profile-name override [NOJIRA] - #378

Closed
tobias0106 wants to merge 1 commit into
mainfrom
feat/service-profile-name-override
Closed

tobias0106 wants to merge 1 commit into
mainfrom
feat/service-profile-name-override

Conversation

@tobias0106

Copy link
Copy Markdown
Contributor

The service-profile job names the ServiceProfile <service-identifier>-<stage>.<service-identifier>-<stage>.svc.cluster.local. Linkerd only applies a profile whose name matches the real Service, so a service whose Kubernetes Service is named differently gets a profile Linkerd ignores. The OCPP processor is one: service-identifier: ocpp-main, but the Service is ocpp-production in ocpp-production (and ocpp-staging on staging).

Adds an optional service-profile-name input to deploy-kotlin, deploy-kotlin-v2 and component-service-profile-kotlin. When set, the job writes it to metadata.name on both new and existing profiles, so the name stays CI-managed instead of being hand-edited in kube-manifests. Leaving it empty keeps today's behaviour for every current caller.

Tested the yq override locally (yq v4.53.2). Not run in CI yet.

Next: monta-app/service-ocpp#3200 sets service-profile-name: ocpp-production.ocpp-production.svc.cluster.local for the processor's production deploy.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tobias0106 tobias0106 closed this Oct 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant