Splice 0.4.8
Good-to-know but no changes needed: Added new helm values persistence.enablePgInitContainer and extraInitContainers allowing configuration around deployment init containers. So far this is implemented only for the…
- A newer release in the 0.4 line: Splice 0.4.25
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
-
Deployment
- Good-to-know but no changes needed: Added new helm values
persistence.enablePgInitContainerandextraInitContainersallowing configuration around deployment init containers. So far this is implemented only for the validator and participant helm charts. The default values for these won’t change your current deployment, so if uninterested you can safely ignore.
- Good-to-know but no changes needed: Added new helm values
-
SV Application
- Add the ability to configure a different topology change delay for the synchronizer parameters and change the default to
250ms. This should have a slight impact on improving the performance of the sequencer. Until a majority of nodes upgrade to0.4.8theReconcileDynamicSynchronizerParametersTriggermight produce warnings.
- Add the ability to configure a different topology change delay for the synchronizer parameters and change the default to
-
Dashboards
- Moved the acknowledgements section from the catchup dashboard to a dedicated dashboard in the
cantonfolder.
- Moved the acknowledgements section from the catchup dashboard to a dedicated dashboard in the
-
Istio Reference Ingress
- Include in the
splice-cluster-ingress-runbookhelm chart an Istio local rate limit filter that adds basic rate limits to a subset of endpoints in Scan. This will be enabled by default if using the helm charts provided for Istio and the Scan ingress is enabled. If not using Istio, the included EnvoyFilter can be used as an inspiration to add rate limits. These rate limits will be expanded in the future to more endpoints.
- Include in the
- Canton Reduced the acknowledgement interval for participants, mediators and sequencers to 10 minutes. This has no impact other than on the acknowlegdement metrics exposed by the sequencer.