Releases: giantswarm/cluster-vsphere
Releases · giantswarm/cluster-vsphere
v0.9.5
Fixed
- Fix templating issues of feature-gates.
v0.9.4
Release v0.9.4 (#131)
v0.9.3
Added
- If
connectivity.network.allowAllEgress
is false (which is the default value), the deny-all network policies for
namespacesgiantswarm
andkube-system
will be applied to the resulting cluster. In terms of API, this is a compatible
change but in terms of internal behavior it can be potentially 💥 Breaking:.
Changed
- Remove
TTLAfterFinished
flag for Kubernetes 1.25 compatibility (enabled by default). - Remove
ExpandPersistentVolumes
flag for Kubernetes 1.27 compatibility (enabled by default). - Remove
logtostderr
for Kubernetes 1.27 compatibility (output is logged to stderr by default).
v0.9.2
v0.9.1
v0.9.0
v0.8.0
Added
- Add IPv4 addresses management (ipam) for WC's
kube-vip-cloud-provider
. If the ipPool is specified, currently one IP is requested from it
and is added to the end of the list for this controller.kube-vip-cloud-provider
is part of our Service-lvl load balancer solution in WC and
at least 1 public IP is always needed for the ingress controller to be able to expose its stuff.