mirror of
https://github.com/dadosfera/maestro.git
synced 2026-08-31 19:58:21 +00:00
Rafael
bb03b18f4a
Oracle Migration Changes: - Create deploy/helm-chart/ directory structure (moved from maestro/) - Create deploy/helmfiles/ directory structure (moved from helmfiles/) - Update chart references in helmfiles from ../maestro to ../helm-chart - Update deploy-manually.yml from Azure AKS to Oracle OKE - Update validate-k8s.yml from Azure AKS to Oracle OKE - Replace Azure CLI with OCI CLI installation and configuration - Replace Azure authentication with OCI authentication using secrets - Replace az aks get-credentials with oci ce cluster create-kubeconfig - Update helmfile paths from helmfiles/ to deploy/helmfiles/ - Remove DockerHub integration (push_to_dockerhub input and related steps) - Change runner from [self-hosted, prd-azure] to [self-hosted, prd-oracle] - Add environment field for proper Oracle deployment environment handling - Add HOME environment variable for OCI CLI Affinity/Resources Standardization: - Add affinity configuration with name=general node selector in values.yaml - Update deployment template to use conditional affinity and resources blocks - Configure staging to disable both affinity and resources (null values) - Enable production to use affinity targeting name=general nodes - Enable production to use standard resource limits (100m-2000m CPU, 1500Mi-2Gi memory) This brings maestro into full compliance with Oracle migration requirements and implements the standardized affinity/resources pattern consistent with in-factory and duc.
25 lines
1.1 KiB
YAML
25 lines
1.1 KiB
YAML
apiVersion: v2
|
|
name: maestro
|
|
description: A Helm chart for Kubernetes
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
|
version: 0.1.0
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application. Versions are not expected to
|
|
# follow Semantic Versioning. They should reflect the version the application is using.
|
|
# It is recommended to use it with quotes.
|
|
appVersion: "1.16.0"
|