forked from bf2fc6cc711aee1a0c2a/kas-fleet-manager
-
Notifications
You must be signed in to change notification settings - Fork 0
/
dynamic-scaling-configuration.yaml
62 lines (62 loc) · 3.33 KB
/
dynamic-scaling-configuration.yaml
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
#This configuration file contains information about each Kafka instance types, dynamic scaling configuration
---
# The version of OpenShift used during installation of newly auto created data plane clusters.
# If the value is empty (default) or not defined, then OpenShift Cluster Manager (OCM) will provision the data plane cluster using the latest version.
# NOTE: temporarily provision new data plane cluster with the latest version of openshift 4.11 available on ocm as the fleetshard operator addon
# is currently incompatible with 4.12.
# To be set back to an empty string once https://issues.redhat.com/browse/MGDSTRM-10450 is resolved.
new_data_plane_openshift_version: "openshift-v4.11.22"
# Whether to auto create a data plane cluster.
# The value is used to control whether kas-fleet-manager (KFM) should trigger the creation of new data plane clusters.
# If it is set to false, then KFM will only perform scale up evaluation without triggering scale up i.e a dry run of cluster's creation.
# If set to true, then KFM will perform scale up evaluation and trigger scaling up if it is needed based on the evaluation results.
enable_dynamic_data_plane_scale_up: false
# Whether to auto delete a data plane cluster cluster
# The value is used to control whether KFM should trigger the deletion of data plane clusters.
# If it is set to false, then KFM will only perform scale down evaluation without triggering scale down i.e a dry run for clusters' deletion.
# If set to true, then KFM will perform scale down evaluation and trigger scaling down if it is needed based on the evaluation results.
enable_dynamic_data_plane_scale_down: false
# compute machine configuration per cloud provider.
# For each cloud provider, two level of informations are provided:
# 1. cluster wide workload e.g ingress controllers, observability operators etc configuration
# 2. kafka workload configuration per instance type.
# Each of the above configuration have the below structure
# compute_machine_type: <cloud provider specific identifier>. This value is the machine type. It is cloud provider specific.
# compute_node_autoscaling: The min and max number of nodes for this workload group. The value can never be zero and min has to be less or equal to maximum.
# min_compute_nodes: <int>
# max_compute_nodes: <int>
compute_machine_per_cloud_provider:
aws:
cluster_wide_workload:
compute_machine_type: m5.2xlarge
compute_node_autoscaling:
min_compute_nodes: 3
max_compute_nodes: 18
kafka_workload_per_instance_type:
standard:
compute_machine_type: r5.xlarge
compute_node_autoscaling:
min_compute_nodes: 3
max_compute_nodes: 18
developer:
compute_machine_type: m5.2xlarge
compute_node_autoscaling:
min_compute_nodes: 1
max_compute_nodes: 3
gcp:
cluster_wide_workload:
compute_machine_type: custom-8-32768
compute_node_autoscaling:
min_compute_nodes: 3
max_compute_nodes: 18
kafka_workload_per_instance_type:
standard:
compute_machine_type: custom-4-32768-ext
compute_node_autoscaling:
min_compute_nodes: 3
max_compute_nodes: 18
developer:
compute_machine_type: custom-8-32768
compute_node_autoscaling:
min_compute_nodes: 1
max_compute_nodes: 3