Remove "m" in the TLS demo. Kine does not support client certificate validation k3s-io/kine#272 (comment)

Author: melgenek

demo/tls/README.md

@@ -2,12 +2,11 @@
 
 This demo illustrates a setup with mutual TLS (mTLS) connections between different components.
 
-K3s, acting as a client, connects to F8N. F8N mimics an etcd server. 
-Simultaneously, F8N acts as a client and connects to FoundationDB (FDB). 
-Both of these connections are secured using mTLS.
+K3s, acting as a client, connects to F8N over HTTPs. F8N mimics an etcd server. 
+Simultaneously, F8N acts as a client and connects to FoundationDB (FDB) via the FDB protocol with mTLS.
 
 ```ascii
-+-----+      mTLS      +-------------+      mTLS      +-----+
++-----+      TLS       +-------------+      mTLS      +-----+
 |     |                |             |                |     |
 | K3S | <------------> |     F8N     | <------------> | FDB |
 |     |                |             |                |     |

demo/tls/docker-compose.yaml

@@ -70,5 +70,3 @@ services:
     environment:
       K3S_DATASTORE_ENDPOINT: "https://f8n-demo:2379"
       K3S_DATASTORE_CAFILE: "/opt/etcd/tls/ca-certificate.pem"
-      K3S_DATASTORE_CERTFILE: "/opt/etcd/tls/client-certificate.pem"
-      K3S_DATASTORE_KEYFILE: "/opt/etcd/tls/client-private-key.pem"

demo/tls/etcd_pki/client-certificate.pem

@@ -23,20 +23,3 @@ openssl x509 -req -in server.csr \
 
 rm server.csr
 ### End Server ###
-
-
-### Client ###
-# Client private key:
-openssl genpkey -algorithm RSA -out client-private-key.pem
-
-# Client certificate signing request (CSR):
-openssl req -new -key client-private-key.pem -out client.csr -config openssl-client.cnf -subj "/C=US/ST=California/L=San Francisco/O=My Organization/OU=IT/CN=example.com"
-
-# Client certificate signed by the CA:
-openssl x509 -req -in client.csr \
-    -CA ca-certificate.pem -CAkey ca-private-key.pem \
-    -out client-certificate.pem -days 3650 -sha256 \
-    -copy_extensions copyall
-
-rm client.csr
-### End Client ###