Skip to content

Releases: kubeslice/kubeslice-controller

v1.5.5

20 Jun 11:22
8182492
Compare
Choose a tag to compare
v1.5.5 Pre-release
Pre-release

What's Changed

Full Changelog: v1.5.4...v1.5.5

v1.3.1-release

28 May 09:38
8ed71c5
Compare
Choose a tag to compare

Patch Release

v1.3.1

28 May 09:39
8ed71c5
Compare
Choose a tag to compare

Patch Release

v1.5.2

18 Apr 09:03
97566d4
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.3.0...v1.5.2

v1.3.0-release

02 Apr 06:05
9d110a1
Compare
Choose a tag to compare

OSS 1.3.0 Release

Full Changelog: v1.3.0-release...v1.3.0-release

v1.3.0

02 Apr 06:07
9d110a1
Compare
Choose a tag to compare

Full Changelog: v1.3.0-release...v1.3.0

OSS 1.3.0 Release

v1.2.1-release

13 Mar 10:55
ff332f5
Compare
Choose a tag to compare

kubeslice OSS 1.2.1 Release

v1.2.1

13 Mar 10:57
ff332f5
Compare
Choose a tag to compare

kubeslice OSS 1.2.1 Release

v1.2.0-release

11 Jan 12:04
ff332f5
Compare
Choose a tag to compare

KubeSlice Supports Cluster Connectivity between Public and Private Clusters
KubeSlice now supports cluster connectivity to private clusters. This feature is currently configurable only using YAML.

With this release, we remove the restriction for the cluster to have at least one node with a public IP address to make it part of the KubeSlice overlay network. Enabling a node with a public IP restricted the application of KubeSlice on private cloud clusters where the virtual private clouds filter out external traffic.

With the new feature, KubeSlice extends its usage to such private cloud clusters through a network load balancer which can be provisioned and managed by all major cloud providers.

v1.2.0

11 Jan 12:05
ff332f5
Compare
Choose a tag to compare

KubeSlice Supports Cluster Connectivity between Public and Private Clusters
KubeSlice now supports cluster connectivity to private clusters. This feature is currently configurable only using YAML.

With this release, we remove the restriction for the cluster to have at least one node with a public IP address to make it part of the KubeSlice overlay network. Enabling a node with a public IP restricted the application of KubeSlice on private cloud clusters where the virtual private clouds filter out external traffic.

With the new feature, KubeSlice extends its usage to such private cloud clusters through a network load balancer which can be provisioned and managed by all major cloud providers.