-
Notifications
You must be signed in to change notification settings - Fork 12
Expand file tree
/
Copy pathopenshift-values.yaml
More file actions
103 lines (93 loc) · 3.37 KB
/
openshift-values.yaml
File metadata and controls
103 lines (93 loc) · 3.37 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
# Testing/CI Values Overlay for Cost Management On-Premise
# =========================================================
# This file provides OVERRIDES for testing and CI environments only.
# It is layered on top of the base values.yaml during helm install.
#
# Purpose:
# - Smaller resource allocations suitable for testing environments
# - Reduced storage sizes (5Gi vs production sizes)
# - CI optimization hints to reduce Helm API lookups
#
# For production deployments, use larger values:
# --set database.ros.storage.size=100Gi
# --set resources.kruize.requests.memory=2Gi
global:
# Cluster domain — detected by install script and passed via --set
# When empty, the chart defaults to "apps.cluster.local" (safe for offline templating)
clusterDomain: "apps.cluster.local" # Set by install script or --set global.clusterDomain=...
# Storage class names — detected by install script from cluster default SC
# Uncomment to override explicitly:
# storageClassNames:
# database: "odf-storagecluster-ceph-rbd"
# kafka: "odf-storagecluster-ceph-rbd"
# storage: "odf-storagecluster-ceph-rbd"
# valkey: "odf-storagecluster-ceph-rbd"
# Reduced resource requirements for testing environment
# Production recommendation: Increase memory for Kruize (2-4Gi)
resources:
application:
requests:
memory: "512Mi"
cpu: "200m"
limits:
memory: "1Gi"
cpu: "500m"
kruize:
requests:
memory: "1Gi"
cpu: "200m"
limits:
memory: "2Gi"
cpu: "1000m"
# Use smaller storage sizes for testing
# Production recommendation: 100Gi for ros/kruize, 50Gi for sources
database:
ros:
storage:
size: "5Gi"
kruize:
storage:
size: "5Gi"
sources:
storage:
size: "5Gi"
# S3-Compatible Object Storage
# ----------------------------
# This chart requires S3-compatible storage. Options:
#
# 1. Manual (production): Set objectStorage.endpoint/port/useSSL/secretName
# and pre-create your credentials secret. The install script will skip
# all S3 auto-detection.
#
# 2. OBC auto-detection: Create an ObjectBucketClaim named "ros-data-ceph"
# in the target namespace. The install script auto-detects it and
# configures endpoints, credentials, and bucket names.
#
# 3. S4 (dev/test): Set S3_ENDPOINT env var before running the install
# script. See docs/development/ocp-dev-setup-s4.md.
#
# 4. Leave empty: The install script attempts NooBaa auto-detection as fallback.
# WARNING: NooBaa's eventual consistency may cause data processing failures.
#
objectStorage:
endpoint: "" # Set manually, or auto-detected by install script
port: 443
useSSL: true
secretName: "" # Set to use a pre-existing credentials secret (skips secret creation)
# JWT Authentication configuration
# Install script detects Keycloak and passes values via --set
jwtAuth:
keycloak:
# url: "" # Set by install script, e.g., "https://keycloak.apps.example.com"
installed: true # Set to false if Keycloak is not deployed
# namespace: "keycloak" # Defaults to "keycloak" when empty
# serviceName: "keycloak-service" # Defaults to "keycloak-service" when empty
# OpenShift Routes configuration
# Override: longer timeout (300s vs 30s default) for large file uploads
gatewayRoute:
enabled: true
annotations:
haproxy.router.openshift.io/timeout: "300s"
tls:
termination: edge
insecureEdgeTerminationPolicy: Redirect