-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add option to disable self-signed transport certs #7925
Changes from all commits
af1f00a
d3a2f6c
296f73a
217d02e
7b45657
38312c4
ea0d5c0
e7473fe
532638b
4ab7f3a
49acd6f
6adb642
8b01596
ef8386b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -80,7 +80,7 @@ If this is undesirable it is also possible to configure node transport certifica | |
|
||
The following example configuration using link:https://cert-manager.io/docs/projects/csi-driver/[cert-manager csi-driver] and link:https://cert-manager.io/docs/projects/trust-manager/[trust-manager] meets these two requirements: | ||
|
||
[source,yaml,subs="attributes"] | ||
[source,yaml,subs="attributes,callouts"] | ||
---- | ||
apiVersion: elasticsearch.k8s.elastic.co/{eck_crd_version} | ||
kind: Elasticsearch | ||
|
@@ -91,7 +91,9 @@ spec: | |
transport: | ||
tls: | ||
certificateAuthorities: | ||
configMapName: trust | ||
configMapName: trust <2> | ||
selfSignedCertificates: | ||
disabled: true <1> | ||
nodeSets: | ||
- name: default | ||
count: 3 | ||
|
@@ -111,16 +113,17 @@ spec: | |
driver: csi.cert-manager.io | ||
readOnly: true | ||
volumeAttributes: | ||
csi.cert-manager.io/issuer-name: ca-cluster-issuer | ||
csi.cert-manager.io/issuer-name: ca-cluster-issuer <2> | ||
csi.cert-manager.io/issuer-kind: ClusterIssuer | ||
csi.cert-manager.io/dns-names: "${POD_NAME}.${POD_NAMESPACE}.svc.cluster.local" | ||
---- | ||
<1> Disables the self-signed certificates generated by ECK for the transport layer. | ||
|
||
The example assumes that a `ClusterIssuer` by the name of `ca-cluster-issuer` exists and a PEM encoded version of the CA certificate is available in a ConfigMap (in the example named `trust`). The CA certificate must be in a file called `ca.crt` inside the ConfigMap in the same namespace as the Elasticsearch resource. | ||
<2> The example assumes that a `ClusterIssuer` by the name of `ca-cluster-issuer` exists and a PEM encoded version of the CA certificate is available in a ConfigMap (in the example named `trust`). The CA certificate must be in a file called `ca.crt` inside the ConfigMap in the same namespace as the Elasticsearch resource. | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the below There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So the idea was that we have a self-signed issuer which issues a certificate ( |
||
The following manifest is only provided to illustrate how these certificates can be configured in principle, using the trust-manager Bundle resource and cert-manager provisioned certificates: | ||
|
||
[source,yaml] | ||
[source,yaml,subs="attributes,callouts"] | ||
---- | ||
apiVersion: trust.cert-manager.io/v1alpha1 | ||
kind: Bundle | ||
|
@@ -154,10 +157,18 @@ spec: | |
--- | ||
apiVersion: cert-manager.io/v1 | ||
kind: ClusterIssuer | ||
metadata: | ||
name: selfsigned-issuer | ||
spec: | ||
selfSigned: {} <1> | ||
--- | ||
apiVersion: cert-manager.io/v1 | ||
kind: ClusterIssuer | ||
metadata: | ||
name: ca-cluster-issuer | ||
spec: | ||
ca: | ||
secretName: root-ca-secret | ||
... | ||
---- | ||
---- | ||
<1> This example, which is meant for illustration purposes only, uses a self-signed issuer as for the root CA and second issuer for the Elasticsearch cluster transport certificates as the cert-manager CSI driver does not support self-signed CAs. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we mention that self-signed issuers cannot be used with the CSI driver? (The
certificaterequests
created by the csi driver do not includecert-manager.io/private-key-secret-name
annotation)