Skip to content

TASK: Validate service Helm charts with local SIT values in CI #110

Closed

Description

@ramioooz

Objective

Make CI validate the Helm values actually used for local Kubernetes SIT releases of the currently deployed API Gateway and domain services.

Exact Scope

  • Work only in these repositories: api-gateway, customer-service, account-service, and ledger-service.
  • Update each existing Helm-validation job to lint and render using that repository's helm/values-sit.yaml.
  • Preserve the current chart names, digital-bank-sit namespace, image-tag override approach, probes, resource settings, and security contexts.
  • Keep the commands deterministic and independent of a live Kubernetes cluster.

Non-goals

  • Do not change Java application behavior, API contracts, Docker runtime behavior, Config Server configuration, or shared infrastructure charts.
  • Do not add UAT/production values files, deployment automation, ingress, autoscaling, network policies, or observability tooling.
  • Do not duplicate the end-to-end local-SIT runbook owned by TASK: Document reproducible local SIT platform setup and verification #108.

Acceptance Criteria

  • Each targeted CI workflow runs helm lint --strict with helm/values-sit.yaml.
  • Each targeted CI workflow renders its chart with helm/values-sit.yaml, the local SIT namespace, and the existing image-tag override.
  • CI remains green for all four repositories.
  • Rendered manifests retain existing non-root security contexts, resources, and Actuator probes.

Verification Commands

Run in each targeted repository, substituting the release name:

helm lint helm --strict --values helm/values-sit.yaml
helm template <release-name> helm \
  --namespace digital-bank-sit \
  --values helm/values-sit.yaml \
  --set image.tag=test

Expected Repository / PR Boundary

One focused pull request per repository: api-gateway, customer-service, account-service, and ledger-service. Link the related PRs to each other in their descriptions; merge order is not significant because the changes are CI-only.

Activity

  1. self-assigned this
    on Aug 2, 2026
  2. added theissue type on Aug 2, 2026
  3. ramioooz commented on Aug 2, 2026

    @ramioooz
    MemberAuthor

    Work started in four independent CI-only pull requests: API Gateway, Customer Service, Account Service, and Ledger Service. Merge order does not matter; this task will move to Done after all four PRs merge and their checks pass.

  4. ramioooz commented on Aug 2, 2026

    @ramioooz
    MemberAuthor

    All four related CI-only PRs are open and independently reviewed. API Gateway, Account Service, and Ledger Service checks have passed; Customer Service container smoke test is still running. The task is now In review and can move to Done only after all four PRs merge.

  5. ramioooz commented on Aug 3, 2026

    @ramioooz
    MemberAuthor

    Resolved by the merged CI-only pull requests: digital-bank-java/api-gateway#16, digital-bank-java/customer-service#32, digital-bank-java/account-service#30, and digital-bank-java/ledger-service#9. Each validates Helm with local SIT values. No rollout was required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions