rancher-charts/charts/harvester-cloud-provider/104.0.3+up0.2.7/dependency_charts/kube-vip/values.yaml

127 lines
3.2 KiB
YAML

# Default values for kube-vip.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
image:
repository: ghcr.io/kube-vip/kube-vip
pullPolicy: IfNotPresent
# Overrides the image tag whose default is the chart appVersion.
# tag: "v0.7.0"
config:
address: ""
# Check https://kube-vip.io/docs/installation/flags/
env:
vip_interface: ""
vip_arp: "true"
lb_enable: "true"
lb_port: "6443"
vip_cidr: "32"
cp_enable: "false"
svc_enable: "true"
svc_election: "false"
vip_leaderelection: "false"
extraArgs: {}
# Specify additional arguments to kube-vip
# For example, to change the Prometheus HTTP server port, use the following:
# prometheusHTTPServer: "0.0.0.0:2112"
envValueFrom: {}
# Specify environment variables using valueFrom references (EnvVarSource)
# For example we can use the IP address of the pod itself as a unique value for the routerID
# bgp_routerid:
# fieldRef:
# fieldPath: status.podIP
envFrom: []
# Specify an externally created Secret(s) or ConfigMap(s) to inject environment variables
# For example an externally provisioned secret could contain the password for your upstream BGP router, such as
#
# apiVersion: v1
# data:
# bgp_peers: "<address:AS:password:multihop>"
# kind: Secret
# name: kube-vip
# namespace: kube-system
# type: Opaque
#
# - secretKeyRef:
# name: kube-vip
extraLabels: {}
# Specify extra labels to be added to DaemonSet (and therefore to Pods)
imagePullSecrets: []
nameOverride: ""
fullnameOverride: ""
serviceAccount:
# Specifies whether a service account should be created
create: true
# Annotations to add to the service account
annotations: {}
# The name of the service account to use.
# If not set and create is true, a name is generated using the fullname template
name: ""
podAnnotations: {}
podSecurityContext: {}
# fsGroup: 2000
securityContext:
capabilities:
add:
- NET_ADMIN
- NET_RAW
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
volumes: []
# Specify additional volumes
# - hostPath:
# path: /etc/rancher/k3s/k3s.yaml
# type: File
# name: kubeconfig
volumeMounts: []
# Specify additional volume mounts
# - mountPath: /etc/kubernetes/admin.conf
# name: kubeconfig
hostAliases: []
# Specify additional host aliases
# - hostnames:
# - kubernetes
# ip: 127.0.0.1
nodeSelector: {}
tolerations:
- effect: NoSchedule
key: node-role.kubernetes.io/control-plane
operator: Exists
affinity: {}
# nodeAffinity:
# requiredDuringSchedulingIgnoredDuringExecution:
# nodeSelectorTerms:
# - matchExpressions:
# - key: node-role.kubernetes.io/master
# operator: Exists
# - matchExpressions:
# - key: node-role.kubernetes.io/control-plane
# operator: Exists
priorityClassName: ""