You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployments/liqo/README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@
11
11
| authentication.awsConfig.secretAccessKey | string |`""`| SecretAccessKey for the Liqo user. |
12
12
| authentication.awsConfig.useExistingSecret | bool |`false`| Use an existing secret to configure the AWS credentials. |
13
13
| authentication.enabled | bool |`true`| Enable/Disable the authentication module. |
14
+
| authentication.tlsCompatibilityMode | bool |`false`| Enable TLS compatibility mode for client certificates and keys. When true, Liqo will use a widely supported algorithm (e.g., RSA/ECDSA) for generating private keys and CSRs instead of Ed25519. Keep disabled by default to preserve current behavior. |
14
15
| common.affinity | object |`{}`| Affinity for all liqo pods, excluding virtual kubelet. |
15
16
| common.extraArgs | list |`[]`| Extra arguments for all liqo pods, excluding virtual kubelet. |
16
17
| common.globalAnnotations | object |`{}`| Global annotations to be added to all resources created by Liqo controllers |
>The cluster ID of the cluster from which peering will be performed
184
184
185
+
`--tls-compatibility-mode`_string_:
186
+
187
+
>TLS compatibility mode for peering-user keys: one of auto,true,false. When auto, liqoctl attempts to detect the controller manager setting. **(default "auto")**
0 commit comments