KubeSlice Controller Opensource Repository: The KubeSlice Controller orchestrates the creation and management of slices on worker clusters.
APACHE-2.0 License
Bot releases are hidden (Show)
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.5.4...v1.5.5
Published by srinivas-avesha 5 months ago
Patch Release
Published by srinivas-avesha 5 months ago
Patch Release
Published by priyank-upadhyay 6 months ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.3.0...v1.5.2
Published by srinivas-avesha 7 months ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.3.0-release...v1.3.0
OSS 1.3.0 Release
Published by srinivas-avesha 7 months ago
OSS 1.3.0 Release
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.3.0-release...v1.3.0-release
Published by srinivas-avesha 7 months ago
kubeslice OSS 1.2.1 Release
Published by srinivas-avesha 7 months ago
kubeslice OSS 1.2.1 Release
Published by mridulgain 8 months ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.2.0-release...v1.2.1
Published by srinivas-avesha 9 months ago
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.
Published by srinivas-avesha 9 months ago
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.
Published by mridulgain 10 months ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.4.0...v1.4.1-alpha
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.4.1-alpha...v1.4.1-alpha-1
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.4.0...v1.4.1
Published by mridulgain 11 months ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v1.3.2...v1.4.0
Published by richiesebastian about 1 year ago
The slice VPN Gateway is an essential component of the slice network service, allowing the slice to connect to secure VPN networks. By default, any new slice created using the KubeSlice Manager or the YAML file will have a duration of 30 days to renew the SliceGateway certificates. You can customize the rotation interval when creating a slice by setting the rotationInterval parameter in the slice configuration YAML file. This interval range is 30 to 90 days.
Additionally, if you need to update the rotation interval at any time, you can modify the rotationInterval parameter in the slice configuration file. This flexibility allows you to align the certificate renewal process with your specific security requirements. Moreover, if you want to initiate the certificate renewal process immediately, you can use the renewBefore option. This option allows you to trigger the certificate renewal process before the expiration of the rotation interval. By specifying an appropriate value for renewBefore parameter in the YAML file, you can ensure that the certificate renewal process starts promptly, helping to maintain the security and compliance of your system.
The VPN cipher can be configured during slice creation using the cipher parameter in the slice configuration YAML file. The cipher value can be set to AES_128_CBC. The default value is AES_256_CBC. This configuration is immutable during the lifetime of a slice
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v0.10.0...v1.1.0-release
Published by richiesebastian over 1 year ago
KubeSlice now records custom metrics that helps in monitoring the slice, and other KubeSlice components. These Prometheus metrics can be configured as alerts using the alert manager.
For more information, see KubeSlice metrics and Prometheus alert rules.
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v0.10.0...v1.0.0
Published by priyank-upadhyay over 1 year ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v0.9.0...v0.10.0
Published by richiesebastian over 1 year ago
These release notes describe the new changes and enhancements in this version.
KubeSlice creates controller events and stores them in the kubeslice-controller and kubeslice-project namespaces.
You can now monitor slice and cluster health
The cert-manager is no longer required to install the KubeSlice Controller on the controller cluster. With this version, the KubeSlice Controller supports upward compatibility. This means that the cert-manager installed does not have any impact on the KubeSlice Controller. However, the cert-manager is still required for the version 0.6.0 and older versions of the KubeSlice Controller to work.
KubeSlice creates controller events and stores them in the kubeslice-controller and kubeslice-project namespaces.
You can now monitor slice and cluster health
The cert-manager is no longer required to install the KubeSlice Controller on the controller cluster. With this version, the KubeSlice Controller supports upward compatibility. This means that the cert-manager installed does not have any impact on the KubeSlice Controller. However, the cert-manager is still required for the version 0.6.0 and older versions of the KubeSlice Controller to work.
The user can edit node ip through cluster spec.
Published by priyank-upadhyay over 1 year ago
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v0.8.5...v0.8.6
Published by priyank-upadhyay over 1 year ago
Cluster.Spec.NetworkInterface
by @priyank-upadhyay in https://github.com/kubeslice/kubeslice-controller/pull/133
Full Changelog: https://github.com/kubeslice/kubeslice-controller/compare/v0.8.0...v0.8.1
Published by bharath-avesha over 1 year ago
Changes needed for mongodb