Skip to content

STORY: Add Kubernetes and Helm deployment polish #66

Closed
2 of 2 issues completed
Closed

Description

@ramioooz

Objective

Make local Kubernetes SIT Helm releases consistent, environment-aware, and validated against the values used for deployment.

Outcome

Every currently deployable service chart has an explicit and repeatable local-SIT values contract, and CI renders the same values that local SIT deployments use.

Scope

  • Establish the missing values-sit.yaml convention for config-server.
  • Validate the local-SIT values for config-server, api-gateway, customer-service, account-service, and ledger-service in their respective CI workflows.
  • Preserve the existing secure pod settings, health probes, resources, and ClusterIP-only service model.

Non-goals

Acceptance Criteria

  • config-server has a dedicated local-SIT Helm values override that preserves the base/default values model.
  • CI linting and rendering uses the local-SIT values files for every currently deployed service chart.
  • Rendered manifests retain the established non-root security context, resource requests/limits, and Actuator probe configuration.
  • Changes are delivered through focused repository PRs with repeatable Helm verification commands.

Activity

  1. added theissue type on Aug 2, 2026
  2. ramioooz commented on Aug 2, 2026

    @ramioooz
    MemberAuthor

    Backlog refinement complete. The Story now has two executable Sprint 0 child tasks:

    The split avoids duplicating #108's local SIT runbook and excludes AWS, UAT, and production work. #109 requires one focused PR in config-server. #110 requires one CI-only PR in each listed service repository; no merge order is required between those PRs.

  3. ramioooz commented on Aug 3, 2026

    @ramioooz
    MemberAuthor

    Completed by TASK #109 (local SIT Helm values and validation) and TASK #110 (service chart validation in CI).

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions