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
|`certificates.certManager.renewBefore`| Time before expiry to renew certificate |`5840h0m0s`|
40
+
|`certificates.certManager.generateCA`| Whether to generate a Certificate Authority |`true`|
41
+
|`certificates.certManager.caSecretName`| Name of the secret containing the CA certificate |`kruise-game-ca`|
42
+
|`certificates.certManager.issuer.generate`| Whether to generate the issuer automatically |`true`|
43
+
|`certificates.certManager.issuer.name`| Name of the certificate issuer |`kruise-ca`|
44
+
|`certificates.certManager.issuer.kind`| Type of the certificate issuer |`ClusterIssuer`|
45
+
|`certificates.certManager.issuer.group`| API group of the certificate issuer |`cert-manager.io`|
34
46
35
47
36
48
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
37
49
50
+
### Certificate Management
51
+
52
+
> **Important**: Kruise Game webhook requires TLS certificates for secure communication. Regardless of which certificate management method you choose, you must ensure that the webhook certificate is signed by a trusted CA certificate, and that the CA certificate is properly configured in the Kubernetes cluster so that the API Server can verify the webhook's identity.
53
+
54
+
Kruise Game supports two methods for webhook certificate management:
55
+
56
+
#### Auto-generated Certificates (Default)
57
+
58
+
By default, kruise-game uses auto-generated certificates for webhook TLS:
0 commit comments