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: cmd/fpga_admissionwebhook/README.md
+2
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,8 @@ controller webhook plugin.
54
54
The default webhook deployment depends on having [cert-manager](https://cert-manager.io/)
55
55
installed. See its installation instructions [here](https://cert-manager.io/docs/installation/kubectl/).
56
56
57
+
> **Note**: The default deployment for the Intel FPGA webhook uses self-signed certificates. For a production cluster, the certificate issuer should be properly set and not use a self-signed method.
58
+
57
59
Also if your cluster operates behind a corporate proxy make sure that the API
58
60
server is configured not to send requests to cluster services through the
59
61
proxy. You can check that with the following command:
> **Note**: The default deployment for the Intel Device Plugin operator uses self-signed certificates. For a production cluster, the certificate issuer should be properly set and not use a self-signed method.
66
+
65
67
The default operator deployment depends on [cert-manager](https://cert-manager.io/) running in the cluster.
66
68
See installation instructions [here](https://cert-manager.io/docs/installation/kubectl/).
Copy file name to clipboardExpand all lines: cmd/sgx_admissionwebhook/README.md
+2
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,8 @@ controller webhook plugin.
32
32
The default webhook deployment depends on having [cert-manager](https://cert-manager.io/)
33
33
installed. See its installation instructions [here](https://cert-manager.io/docs/installation/kubectl/).
34
34
35
+
> **Note**: The default deployment for the Intel SGX webhook uses self-signed certificates. For a production cluster, the certificate issuer should be properly set and not use a self-signed method.
36
+
35
37
Also if your cluster operates behind a corporate proxy make sure that the API
36
38
server is configured not to send requests to cluster services through the
37
39
proxy. You can check that with the following command:
0 commit comments