Ovn Central K8S
- By OpenStack Charmers
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 24.03/edge | 80 | 13 May 2024 | |
| 23.09/stable | 62 | 06 Dec 2023 | |
| 23.09/candidate | 75 | 25 Mar 2024 | |
| 23.09/beta | 75 | 25 Mar 2024 | |
| 23.09/edge | 75 | 23 Feb 2024 | |
| 23.03/stable | 61 | 26 Sep 2023 | |
| 23.03/candidate | 66 | 12 Jan 2024 | |
| 23.03/beta | 66 | 10 Jan 2024 | |
| 23.03/edge | 66 | 13 Dec 2023 | |
| 22.03/beta | 35 | 10 Mar 2023 | |
| 22.03/edge | 43 | 26 May 2023 | |
| 21.09/beta | 20 | 15 Nov 2022 | |
| 21.09/edge | 33 | 20 Jan 2023 |
juju deploy ovn-central-k8s --channel 23.09/stable
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
-
ovsdb-server-election-timer | int
Default: 4
Raft leader election timeout in seconds. The charm allows a value between 1 and 60 seconds. . The Open vSwitch ovsdb-server default of 1 second may not be sufficient for a loaded cluster where the database server may be too busy serving requests to respond to elections in time. . Using a higher value will increase the time to discover a real failure, but you must weigh that against the risk of spurious leader flapping and the unwanted churn that entails. . NOTE: The ovsdb-server will refuse to decrease or increase the value of this timer more than 2x the current value. The charm will compensate for this and decrease / increase the timer in increments, but care should be taken to not decrease / increase the value too much in one operation.
-
ovsdb-server-inactivity-probe | int
Default: 60
Maximum number of seconds of idle time on connection to client before sending an inactivity probe message. The Open vSwitch ovsdb-server default of 5 seconds may not be sufficient depending on type and load of the CMS you want to connect to OVN.