Skip to content

fix(eks): resolve colleague E2E deployment blockers across cluster lifecycle, STS auth, and secrets - #7

Merged
JLCode-tech merged 1 commit into
mainfrom
fix/eks-e2e-colleague-fixes
Oct 30, 2026
Merged

JLCode-tech merged 1 commit into
mainfrom
fix/eks-e2e-colleague-fixes

Conversation

@JLCode-tech

Copy link
Copy Markdown
Owner

Summary

Resolves the root causes identified during the colleague fresh-appliance E2E AWS EKS BNK 2.4.1 deployment:

  • Fix feat(ai-gateway): BNK 2.4.1 AI Governance Console, Manual Schema Alignment, & Live Multi-Cloud Telemetry #2 (Pull Secret & JWT Token Handling):
    • SecretsService.prepare_secrets_for_execution: Exposes file secrets whose name or target_variable_name is cne_pull_secret or jwt_token in value_secrets (in addition to file_secrets), and normalizes raw JSON pull secrets to base64 and unwrapped JWT tokens.
    • KubernetesEngine._helm_registry_login: Accepts both raw JSON ({...}) and base64-encoded cne_pull_secret values for Docker config JSON and GCP service account JSON keys.
    • VariableAssembler.build_variables: Adds Layer 6b fallback to recover cne_pull_secret / jwt_token from project_variables['variable_defaults'] or sibling project modules when missing on a downstream Kubernetes module.
  • Fix feat(docs,system,release): visual tour docs, Forge brand typography, GHCR fork packaging, and v4.0.0 upgrade verification #3 (EKS Cluster Registration, Upsert, Stale Row Pruning, Unregistration & Self-Heal):
    • services/eks_service.py: Extracts region from eks_cluster_arn/cluster_arn ARN prior to falling back to project.region or variable_defaults; generates kubeconfig before looking up existing rows; upserts existing KubernetesCluster rows in-place and prunes stale auto-registered rows in the same project; updates unregister_eks_cluster to match by source_module_id, cluster_name output, or auto-registered project cluster.
    • tasks/opentofu_tasks.py: Snapshots prev_outputs before clearing module outputs on destroy and triggers unregister_eks_cluster for any EKS cluster module (_classify_managed_cluster_module == 'eks' or matches_eks_output_contract(prev_outputs)).
    • EngineRouter: Self-heals missing, stale, or duplicate KubernetesCluster rows in resolve_context and resolve_kubeconfig when an applied project module satisfies the EKS output contract.
  • Fix release(v4.0.0): multi-cloud F5 BNK AI Service Plane, visual tour docs, GHCR packaging, and system upgrade readiness #4 (_inject_eks_bearer_token Region Priority & Credential Fallback):
    • Prioritizes cluster.region over creds_env.get('AWS_REGION') when signing STS presigned bearer tokens and falls back to project_variables['variable_defaults'] / module overrides for AWS credentials when no credential template is bound.
  • Fix Feat/bnk topology canvas #5 (variable_defaults Fallbacks):
    • generate_forge_kubeconfig_local and write_provider_config fall back to project.project_variables['variable_defaults'] for cluster_name/eks_cluster_name and aws_region/region.
  • Fix fix(eks): resolve colleague E2E deployment blockers across cluster lifecycle, STS auth, and secrets #7 (dist/docker-compose.yml Volume Sync):
    • Syncs provider_cache, bfb_cache, ./certs:/app/certs:ro, and TF_PLUGIN_CACHE_DIR into dist/docker-compose.yml.

Verification

  • Added 10 component tests in backend/tests/component/test_eks_e2e_colleague_fixes.py.
  • Verified pytest across unit & component suites and scripts/tests/ibm-compose-drift.test.sh + deploy-version-lockstep.test.sh.

@JLCode-tech
JLCode-tech merged commit 1018010 into main Oct 30, 2026
29 checks passed
@JLCode-tech
JLCode-tech deleted the fix/eks-e2e-colleague-fixes branch October 30, 2026 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant