Problem

Currently, some images used by the cost-onprem chart are built locally, which creates several challenges:
- Manual process prone to human error
- Inconsistent build environments
- No automated testing of image builds
- Difficulty in maintaining image lifecycle
- Manual image tagging and publishing

Solution

Create automated GitHub workflows to build, test, tag, and publish custom images to Quay registry with proper CI/CD practices.

Acceptance Criteria

• [ ] Identify all custom images currently built locally
• [ ] Analyze Dockerfile locations and build contexts
• [ ] Create GitHub Actions workflows for image building
• [ ] Configure Quay registry credentials and repositories
• [ ] Implement semantic versioning for image tags
• [ ] Add build triggers (PR validation, merge to main, release tags)
• [ ] Include image security scanning in workflow
• [ ] Add automated testing for built images
• [ ] Create image build status badges/notifications
• [ ] Document the automated image building process
• [ ] Test end-to-end workflow from code change to published image

Workflow Requirements

• Triggers: Pull requests, main branch pushes, release tags
• Security: Image vulnerability scanning
• Testing: Basic functionality tests for built images
• Tagging: Semantic versioning (v1.0.0), latest for main branch
• Registry: Push to quay.io with appropriate repository structure
• Notifications: Build status updates

Definition of Done

• All custom images have automated build workflows
• Images are published to Quay with proper tagging
• Build process is documented and maintainable
• Security scanning is integrated
• Manual local building is no longer required