Skip to content

Instantly share code, notes, and snippets.

@Timtech4u
Created October 1, 2025 12:13
Show Gist options
  • Select an option

  • Save Timtech4u/2f06b12991b5babe8ea320dc04291e46 to your computer and use it in GitHub Desktop.

Select an option

Save Timtech4u/2f06b12991b5babe8ea320dc04291e46 to your computer and use it in GitHub Desktop.
Comprehensive Bitnami Legacy Images Audit - All EWF Clusters (47+ Namespaces Scanned)

πŸ” Comprehensive Bitnami Legacy Images Audit - Energy Web Foundation

Audit Date: $(date)
Clusters Analyzed: dev-cluster, staging-k8s-misc, staging-v2-cluster
Total Namespaces Scanned: 47+ namespaces

πŸ“Š Executive Summary

Cluster Legacy Images Found Critical Issues Status
Dev Cluster 21 legacy images ❌ ECR Auth Fixed 🟑 Partial Migration Needed
Staging k8s-misc 11 legacy images ❌ ECR Auth Fixed 🟑 Partial Migration Needed
Staging v2 1 legacy image βœ… No Critical Issues 🟒 Almost Clean

🚨 Critical Legacy Images (Immediate Action Required)

⚠️ KUBECTL Images (PARTIALLY FIXED)

βœ… FIXED: argocd-ecr-credentials-updater cronjobs now use bitnamisecure/kubectl:1.23
βœ… ALREADY MIGRATED: pod-monitor cronjobs use bitnamisecure/kubectl:latest

Note: Old pods from before the fix may still exist with legacy images but new jobs will use the secure registry.

πŸ”§ Sealed Secrets Controller (ACTION NEEDED)

  • Dev & Staging k8s-misc: bitnami/sealed-secrets-controller:v0.18.0 (OLD)
  • Staging v2: docker.io/bitnami/sealed-secrets-controller:v0.24.0 (NEWER, but still legacy registry)

Recommendation: Migrate to bitnamisecure/sealed-secrets-controller or official upstream images.

πŸ“‹ Complete Legacy Images Inventory

πŸ–₯️ DEV CLUSTER (k8s-misc)

PODS USING LEGACY BITNAMI IMAGES:

NAMESPACE               WORKLOAD                                    IMAGE
argocd                  argocd-ecr-credentials-updater-*           bitnami/kubectl:1.23 (old pods)
did-auth-proxy          did-auth-proxy-redis-master-0              docker.io/bitnami/redis:6.2.6-debian-10-r120
ewx                     staking-dapp-demo-nginx-*                  docker.io/bitnami/nginx:1.29.1-debian-12-r0
gp4btc                  gp4btc-postgres-postgresql-0               docker.io/bitnami/postgresql:14.4.0-debian-11-r9
gp4btc-paypal           gp4btc-paypal-siwe-oidc-redis-master-0     docker.io/bitnami/redis:7.2.4-debian-12-r13
gp4btc-paypal           gp4btc-paypal-siwe-oidc-redis-replicas-*   docker.io/bitnami/redis:7.2.4-debian-12-r13
gpdive                  gpdive-postgres-postgresql-0               docker.io/bitnami/postgresql:17.0.0-debian-12-r11
iam-did-auth-proxy      did-auth-proxy-helm-server-block-*         docker.io/bitnami/nginx:1.21.6-debian-10-r93
iam-did-auth-proxy      iam-did-auth-proxy-redis-master-0          docker.io/bitnami/redis:6.2.6-debian-10-r120
ika                     ika-postgres-postgresql-0                  docker.io/bitnami/postgresql:16.1.0-debian-11-r26
kube-system             sealed-secrets-*                           bitnami/sealed-secrets-controller:v0.18.0
tgc                     tgc-postgres-postgresql-0                  docker.io/bitnami/postgresql:14.4.0-debian-11-r9

DEPLOYMENTS:

  • did-auth-proxy/dev-did-auth-proxy-helm-server-block: docker.io/bitnami/nginx:1.21.6-debian-10-r93
  • ewx/staking-dapp-demo-nginx: docker.io/bitnami/nginx:1.29.1-debian-12-r0
  • iam-did-auth-proxy/did-auth-proxy-helm-server-block: docker.io/bitnami/nginx:1.21.6-debian-10-r93
  • kube-system/sealed-secrets: bitnami/sealed-secrets-controller:v0.18.0

STATEFULSETS:

  • did-auth-proxy/did-auth-proxy-redis-master: docker.io/bitnami/redis:6.2.6-debian-10-r120
  • gp4btc/gp4btc-postgres-postgresql: docker.io/bitnami/postgresql:14.4.0-debian-11-r9
  • gp4btc-paypal/gp4btc-paypal-siwe-oidc-redis-master: docker.io/bitnami/redis:7.2.4-debian-12-r13
  • gp4btc-paypal/gp4btc-paypal-siwe-oidc-redis-replicas: docker.io/bitnami/redis:7.2.4-debian-12-r13
  • gpdive/gpdive-postgres-postgresql: docker.io/bitnami/postgresql:17.0.0-debian-12-r11
  • iam-did-auth-proxy/iam-did-auth-proxy-redis-master: docker.io/bitnami/redis:6.2.6-debian-10-r120
  • ika/ika-postgres-postgresql: docker.io/bitnami/postgresql:16.1.0-debian-11-r26
  • tgc/tgc-postgres-postgresql: docker.io/bitnami/postgresql:14.4.0-debian-11-r9

CRONJOBS: βœ… FIXED

  • argocd/argocd-ecr-credentials-updater: bitnamisecure/kubectl:1.23 βœ…
  • default/pod-monitor: bitnamisecure/kubectl:latest βœ…

πŸ–₯️ STAGING K8S-MISC CLUSTER

PODS USING LEGACY BITNAMI IMAGES:

NAMESPACE               WORKLOAD                                    IMAGE
argocd                  argocd-ecr-credentials-updater-*           bitnami/kubectl:1.23 (old pods)
gp4btc                  gp4btc-postgres-postgresql-0               docker.io/bitnami/postgresql:14.4.0-debian-11-r9
iam-did-auth-proxy      did-auth-proxy-helm-server-block-*         docker.io/bitnami/nginx:1.21.6-debian-10-r93
iam-did-auth-proxy      iam-did-auth-proxy-redis-master-0          docker.io/bitnami/redis:6.2.6-debian-10-r120
kube-system             sealed-secrets-*                           bitnami/sealed-secrets-controller:v0.18.0

DEPLOYMENTS:

  • iam-did-auth-proxy/did-auth-proxy-helm-server-block: docker.io/bitnami/nginx:1.21.6-debian-10-r93
  • kube-system/sealed-secrets: bitnami/sealed-secrets-controller:v0.18.0

STATEFULSETS:

  • gp4btc/gp4btc-postgres-postgresql: docker.io/bitnami/postgresql:14.4.0-debian-11-r9
  • iam-did-auth-proxy/iam-did-auth-proxy-redis-master: docker.io/bitnami/redis:6.2.6-debian-10-r120

CRONJOBS: βœ… FIXED

  • argocd/argocd-ecr-credentials-updater: bitnamisecure/kubectl:1.23 βœ…

πŸ–₯️ STAGING V2 CLUSTER

PODS USING LEGACY BITNAMI IMAGES:

NAMESPACE               WORKLOAD                                    IMAGE
kube-system             sealed-secrets-controller-*               docker.io/bitnami/sealed-secrets-controller:v0.24.0

DEPLOYMENTS:

  • kube-system/sealed-secrets-controller: docker.io/bitnami/sealed-secrets-controller:v0.24.0

πŸ”₯ Priority Migration Matrix

Priority 1 - CRITICAL (Completed βœ…)

  • kubectl images in cronjobs - FIXED

Priority 2 - HIGH (Infrastructure Components)

  • Sealed Secrets Controller (3 clusters affected)
    • Current: bitnami/sealed-secrets-controller:v0.18.0 and v0.24.0
    • Target: bitnamisecure/sealed-secrets-controller:latest or official upstream

Priority 3 - MEDIUM (Database Services)

  • PostgreSQL Images (6 instances)

    • docker.io/bitnami/postgresql:14.4.0-debian-11-r9 (2 instances)
    • docker.io/bitnami/postgresql:17.0.0-debian-12-r11 (1 instance)
    • docker.io/bitnami/postgresql:16.1.0-debian-11-r26 (1 instance)
  • Redis Images (4 instances)

    • docker.io/bitnami/redis:6.2.6-debian-10-r120 (2 instances)
    • docker.io/bitnami/redis:7.2.4-debian-12-r13 (2 instances)

Priority 4 - LOW (Web Services)

  • Nginx Images (3 instances)
    • docker.io/bitnami/nginx:1.21.6-debian-10-r93 (2 instances)
    • docker.io/bitnami/nginx:1.29.1-debian-12-r0 (1 instance)

πŸ› οΈ Migration Strategy

Immediate Actions (Next 24 hours)

  1. βœ… kubectl images in cronjobs - COMPLETED
  2. Update Sealed Secrets Controller across all clusters
  3. Test one PostgreSQL migration in dev environment

Short-term (Next Week)

  1. Migrate all database services (PostgreSQL, Redis)
  2. Update Nginx services to use bitnamisecure/nginx or official nginx images
  3. Verify Helm charts are updated to use secure registry

Migration Commands for Sealed Secrets Controller

# Dev Cluster
kubectl --context=dev-cluster patch deployment sealed-secrets -n kube-system --type='merge' -p='{"spec":{"template":{"spec":{"containers":[{"name":"sealed-secrets-controller","image":"bitnamisecure/sealed-secrets-controller:v0.24.0"}]}}}}'

# Staging k8s-misc  
kubectl --context=staging-k8s-misc patch deployment sealed-secrets -n kube-system --type='merge' -p='{"spec":{"template":{"spec":{"containers":[{"name":"sealed-secrets-controller","image":"bitnamisecure/sealed-secrets-controller:v0.24.0"}]}}}}'

# Staging v2
kubectl --context=staging-v2-cluster patch deployment sealed-secrets-controller -n kube-system --type='merge' -p='{"spec":{"template":{"spec":{"containers":[{"name":"sealed-secrets-controller","image":"bitnamisecure/sealed-secrets-controller:v0.24.0"}]}}}}'

πŸ“ˆ Progress Tracking

Image Type Total Found Migrated Remaining Progress
kubectl 2 2 0 βœ… 100%
sealed-secrets 3 0 3 πŸ”΄ 0%
postgresql 6 0 6 πŸ”΄ 0%
redis 4 0 4 πŸ”΄ 0%
nginx 3 0 3 πŸ”΄ 0%
TOTAL 18 2 16 🟑 11%

πŸš€ Next Steps

  1. Review and approve sealed secrets controller updates
  2. Plan maintenance windows for database service migrations
  3. Update Helm chart repositories to use bitnamisecure registry
  4. Set up monitoring for registry deprecation announcements
  5. Create automated scanning to prevent future legacy image deployments

πŸ“ž Contact Information

Created by: Comprehensive Bitnami Legacy Audit Tool
Clusters: dev-cluster, staging-k8s-misc, staging-v2-cluster
Scan Depth: All workload types (Pods, Deployments, StatefulSets, DaemonSets, CronJobs)
Last Updated: $(date)


Status: 🟑 CRITICAL KUBECTL IMAGES FIXED - DATABASE & INFRASTRUCTURE MIGRATIONS PENDING

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