Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create minimal production.yaml #319

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

pvannierop
Copy link

Problem

Then initializing a new project the production.yaml file is created that will hold the deployment-specific configuration. At present, the entire base.yaml contents are reflected in production.yaml. This makes it difficult to spot the deployment-specific configuration.

Solution

This PR will filter base.yaml to only contain the _install: fields and the deployment specific fields atomicInstall, kubeContext, server_name and maintainer_email. It will look like this:

atomicInstall: true
kubeContext: default
server_name: example.com
maintainer_email: [email protected]
mongodb:
  _install: true
elasticsearch:
  _install: true
graylog:
  _install: true
fluent_bit:
  _install: true
cert_manager:
  _install: true
kube_prometheus_stack:
  _install: true
nginx_ingress:
  _install: true
kafka_manager:
  _install: false
cert_manager_letsencrypt:
  _install: true
cp_zookeeper:
  _install: true
cp_kafka:
  _install: true
cp_schema_registry:
  _install: true
catalog_server:
  _install: true
radar_home:
  _install: true
postgresql:
  _install: true
management_portal:
  _install: true
kratos:
  _install: true
kratos_ui:
  _install: true
app_config:
  _install: true
app_config_frontend:
  _install: true
radar_appserver_postgresql:
  _install: false
radar_appserver:
  _install: false
radar_fitbit_connector:
  _install: false
radar_oura_connector:
  _install: false
radar_rest_sources_authorizer:
  _install: false
radar_rest_sources_backend:
  _install: false
timescaledb:
  _install: true
radar_grafana:
  _install: false
data_dashboard_backend:
  _install: false
radar_jdbc_connector_grafana:
  _install: false
radar_jdbc_connector_data_dashboard_backend:
  _install: false
radar_jdbc_connector_realtime_dashboard:
  _install: false
ksql_server:
  _install: false
radar_gateway:
  _install: true
radar_backend_monitor:
  _install: false
radar_backend_stream:
  _install: false
radar_integration:
  _install: false
redis:
  _install: true
minio:
  _install: true
radar_s3_connector:
  _install: true
s3_proxy:
  _install: false
radar_output:
  _install: true
radar_upload_postgresql:
  _install: true
radar_upload_connect_backend:
  _install: true
radar_upload_connect_frontend:
  _install: true
radar_upload_source_connector:
  _install: true
ccSchemaRegistryProxy:
  _install: false
radar_push_endpoint:
  _install: false
velero:
  _install: false

@pvannierop pvannierop self-assigned this Aug 28, 2024
@keyvaann keyvaann changed the base branch from main to dev August 28, 2024 13:39
@pvannierop pvannierop force-pushed the feature/minimal-production-yaml branch from ae052f0 to 8e62d3d Compare August 29, 2024 07:34
@keyvaann
Copy link
Collaborator

You can run diff base.yaml production.yaml to spot the deployment specific changes.
With the minimal production.yaml you need to keep copying the settings from base.yaml to production.yaml and I suspect it will soon become just like base.yaml. The idea of base.yaml is to be as minimal as possible so it would reflect the deployment specific changes.

@pvannierop pvannierop force-pushed the feature/minimal-production-yaml branch from 8e62d3d to adad551 Compare October 16, 2024 15:00
Production.yaml no longer repeats base chart versions (and other items) defined in the RADAR-Kubenetes release. From here on it will only be used to indicate deviations from base.yaml.
@pvannierop pvannierop force-pushed the feature/minimal-production-yaml branch from adad551 to 9931596 Compare October 16, 2024 15:00
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.

2 participants