Releases: kubeslice/worker-operator
v1.1.0-release
Slice VPN Key rotation
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.
What's Changed
- fix(): Initialize labels field as an empty map by @Rahul-D78 in #267
- fix(): fix gateway rebalancing by @gourishkb in #271
- [WIP] VPN Key Rotation Reconciler by @YachikaRalhan in #257
- fix(): updated ctrl apis dependency by @YachikaRalhan in #274
- fix(): fsm bug fixes - v1 by @rahulsawra98 in #276
- fix(): recycler name as gw pod name by @YachikaRalhan in #277
- fix(): disabled rebalancing by @YachikaRalhan in #279
Full Changelog: v1.0.4...v1.1.0-release
v1.0.4
Releasing new master
v1.0.3
Releasing latest master.
v1.0.2
- slice redesign
- health check enhancement
v1.0.1
fix(): releasing latest changes
v1.0.0
What's New
These release notes describe the new changes and enhancements in this version.
Worker Operator-generated Events
The Worker Operator generates events in the kubeslice-system namespace. The events can be retrieved using the corresponding command. For more information, see the Worker Operator events.
KubeSlice Metrics
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.
v0.21.0-release
What's New
These release notes describe the new changes and enhancements in this version.
Slice and Cluster Health
You can now monitor slice and cluster health
Service Export Discovery
To identify the exported services from a worker cluster that have different names other than the slice.local name, a new property called aliases has been introduced as part of the service export configuration.
Edit Node IP
The node IP for the worker cluster that is registered with the controller can now be edited. If KubeSlice could not detect a node IP during registration, you can enter it by editing a cluster.
v0.18.8-rc
feat(): Adding aliases to service export (#192) There is a requirement to identify exported services with arbitrary names instead of slice.local names. This can be achieved by providing an alias field in the service export spec section so that the users can give any name that they desire to the service being exported from a cluster. Added a new field to hold alias names to the service import and export CRDs. Signed-off-by: Bharath Horatti <[email protected]>
v0.18.6
Support alias names in exported services.
release faridabad
slice gw update context in retry loop