Repository navigation
Migrate Config Server to Git-backed configuration - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
platform-configGit repositoryWhy
Client configuration must be independently versioned and promoted without rebuilding Config Server. Separating configuration also prevents the service image and repository from becoming a second source of truth.
Runtime impact
Local execution defaults to a sibling
platform-configcheckout. Kubernetes deployments require theconfig-server-git-credentialsSecret with repository-scoped read-only credentials. The startup probe uses the liveness health group so Git health latency does not block process startup checks.Validation
./mvnw --batch-mode --no-transfer-progress verifyhelm lint helm --strictplatform-configcommitCloses #10