hypershift/values-hypershift.yaml at main · validatedpatterns-sandbox/hypershift · GitHub

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
# Override values for HyperShift
# Define the s3 bucket information
global:
  hypershift:
    createBucket: true
    oidc:
# OIDC bucket information: provide region and bucketName
      region: "s3-bucket-region"
      bucketName: "s3-bucket-name"

# GitHub organization(s) — shared by oauth and group-sync
  github:
    orgs:
    - name: 'gh-org-name'
      # Teams: Group Sync uses them for OpenShift groups. OAuth uses org/team slugs
      # for login when this list is non-empty; otherwise OAuth allows the whole org.
      teams: []

# register a GitHub oAuth application: https://github.com/settings/applications/new
# configure oauth provider: https://docs.openshift.com/container-platform/4.15/authentication/understanding-identity-provider.html
#
# The default configuration uses github as the provider
  oauth:
    type: GitHub
    secretName: ocp-github-oauth
    github:
      clientID: 'gh-oauth-client-id'

# Group Sync Operator — syncs GitHub teams to OpenShift groups.
# Vault secret githubGroupSync: `appId` = GitHub App ID (settings/apps → About), not installation ID;
# `privateKey` = app PEM. The operator resolves org installation from `global.github.orgs[].name`.
  groupsync:
    secretName: github-group-sync
    github:
      credentialsSecretName: github-group-sync
      url: https://api.github.com/

# KubeletConfig (charts/all/kubelet-config).
# If cluster is compact 3-node hub: all nodes are on the master
# MachineConfigPool; the worker pool is empty, so targetPool must be master.
kubelet:
  targetPool: worker

# Cluster Autoscaling Configuration
# Enable autoscaling to automatically adjust cluster size based on workload demands
autoscaling:
  clusterAutoscaler:
    # Set to true to enable cluster autoscaling
    enabled: false
    # Balance nodes across similar MachineSets (e.g., across availability zones)
    balanceSimilarNodeGroups: true
    # Allow scale-down of nodes running pods with emptyDir volumes
    skipNodesWithLocalStorage: false
    resourceLimits:
      # Maximum total nodes allowed in the cluster
      maxNodesTotal: 24
      cores:
        min: 8
        max: 128
      memory:
        min: 32
        max: 512
    scaleDown:
      enabled: true
      # Time to wait after scale up before considering scale down
      delayAfterAdd: "10m"
      # Node utilization threshold (0.0-1.0) below which nodes are candidates for removal
      utilizationThreshold: "0.6"

  # Define MachineAutoscalers for each MachineSet to autoscale
  # Uncomment and configure based on your cluster's MachineSets
  machineAutoscalers: []
  # Example:
  # - name: worker-autoscaler-1a
  #   enabled: true
  #   machineSetName: <cluster-name>-worker-<zone>
  #   minReplicas: 0
  #   maxReplicas: 6

# Set rbac.create to false if you want to skip creation of role/rolebinding.
rbac:
  create: true
# Provide a list of users and/or groups to add to the clusterrolebinding
  users: []
  groups: []
  sudoerGroups:
  - Engineering