Here is Vita Mojo's organisation map

• Infrastructure
  • Kubernetes
  • Observability
  • Databases
    • Redis
• Services
  • Backend Services
  • Frontend Services
  • Point of Sale
• CI/CD

Kubernetes cluster is managed by Deckhouse. There are several ways to access and manage the cluster:

• Kubernetes Dashboard (Web UI)

• kubeconfig (CLI access) Generate and download your kubeconfig file to use with kubectl command-line tool.

• Deckhouse Console (Management interface)

• Deckhouse CLI

Kubernetes Infrastructure Repository: k8s-infra

This repository contains Helm charts and Kubernetes manifests for infrastructure components:

• backup-restic - Backup solutions using Restic
• deckhouse - Deckhouse module configurations and cluster resources
• istio - Istio service mesh configuration
• knative - Knative serving configuration
• knative-operator - Knative operator deployment
• madison-nginx-proxy - Nginx proxy configuration
• non-managed-resources - Resources not managed by Helm
• redis - Redis Failover cluster deployments
• redis-operator - Redis Operator deployment
• signadot - Signadot sandbox environment configuration
• user-authz - User authorization configuration

• Grafana
• Prometheus
• Kiali (Istio observability dashboard)

Namespace: infra-redis-main

Redis cluster is managed by Redis Operator using RedisFailover Custom Resource (CR). The operator automatically manages Redis instances through Redis Sentinel.

Repositories:

• Redis Operator
• Redis Failover

Cluster Components:

• RFR (Redis Failover Redis) - Redis itself, a group of instances (master + replicas) with persistent storage
• RFS (Redis Failover Sentinel) - Redis Sentinel, which selects the master and performs automatic failover. Sentinel-aware clients can work directly through Sentinel
• Sentinel Proxy - proxy for connecting classic Redis clients that don't support Sentinel directly

Connection Endpoints:

• Redis Sentinel Proxy (for regular Redis clients that don't support Sentinel):
  • Internal:

  redis-sentinel-proxy.infra-redis-main:6379
  

  • External LoadBalancer:

  a4906934f213b4f45938ec1eddb060c5-d57d3c67ce52df3d.elb.eu-west-1.amazonaws.com:6379
  

• Redis Sentinel (for sentinel-aware clients):

  rfs-redis.infra-redis-main:26379
  

To connect you should use credentials, which are encrypted with werf secrets

• catalog-service
• loyalty-service
• media-service
• order-service
• payment-service
• tenant-service
• user-auth-service

• collection-tv-v3
• management-dashboard-v2
• online-store
• tenants-management-ui

• pos2

CI/CD pipelines and workflows for the organization are managed through GitHub Actions.

Repositories:

• github-workflows - Shared GitHub Actions workflows and reusable pipeline definitions