Skip to content

Code: Fix blue-green deployment to use ConfigHub-only commands #4

Description

@monadic

Priority: MEDIUM

Description

The blue-green deployment script uses direct kubectl commands (kubectl patch, kubectl scale) which violates the ConfigHub-only deployment principle.

Impact

  • Bypasses ConfigHub audit trail
  • Creates drift between ConfigHub state and actual state
  • Violates DevOps-as-Apps principles

Required Fix

Replace kubectl commands with ConfigHub operations:

# Instead of: kubectl patch service
cub unit update service-unit --patch --data '{...}'

# Instead of: kubectl scale deployment
cub unit update deployment-unit --patch --data '{"spec":{"replicas":3}}'

Acceptance Criteria

  • No kubectl commands in blue-green script
  • All changes go through ConfigHub
  • Maintain zero-downtime deployment capability

References

  • DevOps-as-Apps requirement for ConfigHub-only
  • Original finding in CODE-REVIEW.md

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions