DirectorySecurity AdvisoriesPricing
Sign in
Directory
kube-vip-cloud-provider logoHELM

kube-vip-cloud-provider

Helm chart
Last changed
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.

Overview
Chart versions
Default values
Chart metadata
Images

Tag:

1
# Default values for kube-vip-cloud-provider.
2
# This is a YAML-formatted file.
3
# Declare variables to be passed into your templates.
4
5
replicasCount: 1
6
image:
7
repository: cgr.dev/chainguard-private/kube-vip-cloud-provider
8
pullPolicy: IfNotPresent
9
# Overrides the image tag whose default is the chart appVersion.
10
# tag: "v0.0.4"
11
12
tag: latest@sha256:c8bcd18a17d6f8bab70b6b9eec083a441e4ca0b3a47c74d4a503ff21d60bcb0c
13
imagePullSecrets: []
14
# Custom namespace to override the namespace for the deployed resources.
15
namespaceOverride: ""
16
## Cloud Provider ConfigMap
17
## CIDR blocks , IP ranges [start address - end address]
18
## Multiple pools by CIDR per Namespace, Multiple IP ranges per Namespace (handles overlapping ranges)
19
20
# cm:
21
# data:
22
# cidr-default: 192.168.0.200/29
23
# range-development: 192.168.0.210-192.168.0.219
24
# cidr-finance: 192.168.0.220/29,192.168.0.230/29
25
# cidr-global: 192.168.0.240/29
26
cm:
27
data: {}
28
# By default, kube-vip-cloud-provider will use a configMap automatically generated from .Values.cm.data.
29
# If .Values.configMapName is defined, it will use that configMap instead, which you must create yourself.
30
configMapName: ""
31
# Specify additional environment variables to kube-vip-cloud-provider
32
# For example, set custom loadbalancerClass
33
# KUBEVIP_CUSTOM_LOADBALANCERCLASS_NAME: custom-class
34
extraEnv: {}
35
# Specify additional arguments to kube-vip-cloud-provider
36
extraArgs: {}
37
annotations: {}
38
resources:
39
requests:
40
cpu: 50m
41
memory: 64Mi
42
limits:
43
cpu: 100m
44
memory: 128Mi
45
# Node selector allows you to constrain a Pod to be scheduled on nodes with specific labels.
46
# If specified, the nodeSelector will be applied alongside the defined affinity rules.
47
# If left empty, the nodeSelector will not be applied, and the Pod can be scheduled on any node.
48
49
# nodeSelector:
50
# disktype: ssd
51
# nodepool: system
52
# critical-addons-only: "true"
53
nodeSelector: {}
54
tolerations:
55
- key: node-role.kubernetes.io/master
56
effect: NoSchedule
57
- key: node-role.kubernetes.io/control-plane
58
effect: NoSchedule
59
affinity:
60
nodeAffinity:
61
preferredDuringSchedulingIgnoredDuringExecution:
62
- weight: 10
63
preference:
64
matchExpressions:
65
- key: node-role.kubernetes.io/control-plane
66
operator: Exists
67
- weight: 10
68
preference:
69
matchExpressions:
70
- key: node-role.kubernetes.io/master
71
operator: Exists
72
priorityClassName: ""
73
# Enable loadbalancerClass to only reconcile services that have
74
# spec.loadbalancerClass: kube-vip.io/kube-vip-class
75
enableloadbalancerClass: false
76

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 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.