Skip to content

BUG: configure API Gateway Redis endpoint for SIT #249

Closed
digital-bank-java/config-repo
#47

Description

@ramioooz

Problem

API Gateway readiness in SIT returns HTTP 503 because Spring Data Redis defaults to localhost:6379. The existing shared Redis chart is present in infra-sit and is the documented runtime dependency, but the SIT Config Repository does not provide the Kubernetes Service host.

Parent and Sprint

  • Parent: .github#34 Observability & Resilience
  • Sprint: Sprint 6 - Operational Resilience and Observability
  • Service: config-repo / api-gateway
  • Assignee: ramioooz

Scope

  • Add the SIT-only Redis host and port to the API Gateway configuration.
  • Keep UAT/PROD values environment-specific and out of this local SIT change.
  • Do not add a second Redis deployment, CI workflow, or redundant test suite.
  • Validate Config Server rendering and API Gateway health after rollout.

Acceptance Criteria

  • api-gateway/sit resolves spring.data.redis.host=redis and port 6379.
  • API Gateway's Redis health indicator is UP in digital-bank-sit.
  • The Gateway health endpoint returns HTTP 200 while existing routes remain available.
  • Config Repository diff validation passes.

Activity

  1. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Implementation PR: https://github.com/digital-bank-java/config-repo/pull/47\n\nThe existing infra-sit Redis chart is now installed and healthy in digital-bank-sit. PR #47 adds the missing api-gateway/sit spring.data.redis.host=redis and port=6379 configuration. After review/merge, restart or roll the API Gateway and verify Redis health plus HTTP 200 readiness.

  2. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Post-merge SIT verification (2026-09-07):

    • Config Server fetched the merged Config Repo main revision containing spring.data.redis.host: redis.
    • API Gateway was restarted so its startup-loaded configuration took effect.
    • Rollout completed successfully.
    • Through the API Gateway port-forward on local port 18080, all of the following returned HTTP 200 with status=UP: /actuator/health, /config-server/actuator/health, /customer-service/actuator/health, /account-service/actuator/health, /auth-service/actuator/health, /mfa-service/actuator/health, /transaction-service/actuator/health, and /payment-service/actuator/health.

    No secret values were read or recorded. The existing issue and Project item remain closed/Done.

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

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions