kube-vip
Helm chart
Request a free trial
Contact our team to test out this Helm chart and related images for free. Please also indicate any other images you would like to evaluate.
Tag:
1
# Default values for kube-vip.
2
# This is a YAML-formatted file.
3
# Declare variables to be passed into your templates.
4
image:
5
repository: cgr.dev/chainguard-private/kube-vip
6
pullPolicy: IfNotPresent
7
# Overrides the image tag whose default is the chart appVersion.
8
# tag: "v0.7.0"
9
10
tag: latest@sha256:4177829148f486e77ea4f1812e052e80a3451cb9b94be0a053b69b62f6423a11
11
config:
12
address: ""
13
# Check https://kube-vip.io/docs/installation/flags/
14
env:
15
vip_interface: ""
16
vip_arp: "true"
17
lb_enable: "true"
18
lb_port: "6443"
19
vip_subnet: "32"
20
cp_enable: "false"
21
svc_enable: "true"
22
svc_election: "false"
23
vip_leaderelection: "false"
24
prometheus_server: ":2112"
25
extraArgs: {}
26
# Specify additional arguments to kube-vip
27
# For example, to change the Prometheus HTTP server port, use the following:
28
# prometheusHTTPServer: "0.0.0.0:2112"
29
30
envValueFrom: {}
31
# Specify environment variables using valueFrom references (EnvVarSource)
32
# For example we can use the IP address of the pod itself as a unique value for the routerID
33
# bgp_routerid:
34
# fieldRef:
35
# fieldPath: status.podIP
36
37
envFrom: []
38
# Specify an externally created Secret(s) or ConfigMap(s) to inject environment variables
39
# For example an externally provisioned secret could contain the password for your upstream BGP router, such as
40
#
41
# apiVersion: v1
42
# data:
43
# bgp_peers: "<address:AS:password:multihop>"
44
# kind: Secret
45
# name: kube-vip
46
# namespace: kube-system
47
# type: Opaque
48
#
49
# - secretKeyRef:
50
# name: kube-vip
51
52
extraLabels: {}
53
# Specify extra labels to be added to DaemonSet (and therefore to Pods)
54
55
annotations: {}
56
# Specify annotations to be added to DaemonSet
57
58
imagePullSecrets: []
59
nameOverride: ""
60
fullnameOverride: ""
61
# Custom namespace to override the namespace for the deployed resources.
62
namespaceOverride: ""
63
serviceAccount:
64
# Specifies whether a service account should be created
65
create: true
66
# Annotations to add to the service account
67
annotations: {}
68
# The name of the service account to use.
69
# If not set and create is true, a name is generated using the fullname template
70
name: ""
71
podAnnotations: {}
72
podSecurityContext: {}
73
# fsGroup: 2000
74
75
securityContext:
76
capabilities:
77
add:
78
- NET_ADMIN
79
- NET_RAW
80
drop:
81
- ALL
82
updateStrategy:
83
type: RollingUpdate
84
rollingUpdate:
85
maxUnavailable: 1
86
resources: {}
87
# We usually recommend not to specify default resources and to leave this as a conscious
88
# choice for the user. This also increases chances charts run on environments with little
89
# resources, such as Minikube. If you do want to specify resources, uncomment the following
90
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
91
# limits:
92
# cpu: 100m
93
# memory: 128Mi
94
# requests:
95
# cpu: 100m
96
# memory: 128Mi
97
98
volumes: []
99
# Specify additional volumes
100
# - hostPath:
101
# path: /etc/rancher/k3s/k3s.yaml
102
# type: File
103
# name: kubeconfig
104
105
volumeMounts: []
106
# Specify additional volume mounts
107
# - mountPath: /etc/kubernetes/admin.conf
108
# name: kubeconfig
109
110
hostAliases: []
111
# Specify additional host aliases
112
# - hostnames:
113
# - kubernetes
114
# ip: 127.0.0.1
115
116
nodeSelector: {}
117
tolerations:
118
- effect: NoSchedule
119
key: node-role.kubernetes.io/control-plane
120
operator: Exists
121
affinity: {}
122
# nodeAffinity:
123
# requiredDuringSchedulingIgnoredDuringExecution:
124
# nodeSelectorTerms:
125
# - matchExpressions:
126
# - key: node-role.kubernetes.io/master
127
# operator: Exists
128
# - matchExpressions:
129
# - key: node-role.kubernetes.io/control-plane
130
# operator: Exists
131
132
podMonitor:
133
enabled: false
134
labels: {}
135
annotations: {}
136
priorityClassName: ""
137
The trusted source for open source
Talk to an expertProduct
Customers
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.