Skip to main content

HECO Details

HECO Client Environment Updates

Service Principal Integration

A dedicated service principal has been created in Azure to enable HECO environments to pull both Helm charts and Docker images from the ACR container registry omni777.

Key Resources

Helm Charts

Source Code

  • HECO Branch: HECO Branch
  • Contains: Latest code specifically used in HECO deployments

Deployment Process for HECO

Creating New HECO Deployments

  1. Navigate to the Release Pipeline
  2. Run the release pipeline to create a new version for HECO

Critical Requirement

⚠️ Important: Ensure the release-35665 tag is always available in the omni777 container registry. All deployment charts in HECO expect this build tag. If unavailable, it could cause the HECO cluster to enter a bad state.

HECO Deployment Files

  • Repository: HECO Charts Repository
  • Contents: YAML deployment files collected from the client over time
  • Purpose: Debug various issues and provide client backups
  • Note: May not be the latest version but provides comprehensive cluster state information

Historical Note: Backup functionality was initially implemented but later removed as it was causing serious issues with cloud-native PostgreSQL deployments.


Important Issues and Resolutions

Keycloak Version Upgrade Considerations

Known Issues

  • Version Upgrades: Keycloak version upgrades can break multiple components and cause significant issues
  • Cloud-Native PostgreSQL: Particular problems arise when used with cloud-native PostgreSQL deployments
  • Backup Complications: Adding backup functionality can send clusters into an unrecoverable error state

Recommendations

  • Exercise extreme caution when upgrading Keycloak versions
  • Thoroughly test in development environments before production deployment
  • Avoid implementing backup features that may interfere with cloud-native PostgreSQL operations

Legacy Documentation Status

Most older documentation remains valid for HECO client environments. The primary updates documented above focus on:

  • Infrastructure migration to Azure services
  • Container registry consolidation
  • Service principal authentication for HECO environments

For any questions or additional information, please contact the TechOps team or refer to the Azure DevOps repositories linked throughout this documentation.