From 4200dfaa836b4706053349f0ce946fc8fdcbce31 Mon Sep 17 00:00:00 2001 From: Shaker Gilbert Date: Tue, 22 Oct 2019 08:19:45 -0400 Subject: [PATCH 1/5] Updated Docker EE Version Rolled version 17.03 to 18.09 which is the minimum supported Docker EE version. --- docs/system-reqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/system-reqs.md b/docs/system-reqs.md index 9e4a4101..44775bb8 100644 --- a/docs/system-reqs.md +++ b/docs/system-reqs.md @@ -18,7 +18,7 @@ Versions starting at v1.0 have been tested and are supported on the following Li **Supported software versions:** -* Docker EE 17.03 or later is supported +* Docker EE 18.09 or later is supported * Python 2.7 * etcd 2.x From 69ca1c45d2b7744e14a8f72858bfd4f796d8ef41 Mon Sep 17 00:00:00 2001 From: Shaker Gilbert Date: Tue, 22 Oct 2019 09:49:45 -0400 Subject: [PATCH 2/5] Create example hpe-etcd.yaml Generated a simple etcd.yaml file for /etc/kubernetes/manifests for the HPE flexvolume driver. --- docs/example-hpe-etcd.md | 71 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 docs/example-hpe-etcd.md diff --git a/docs/example-hpe-etcd.md b/docs/example-hpe-etcd.md new file mode 100644 index 00000000..a1c78655 --- /dev/null +++ b/docs/example-hpe-etcd.md @@ -0,0 +1,71 @@ +## Example YAML for HPE-ETCD +After generating the file, place it in the /etc/kubernetes/manifests directory to automaticly start the pod and have it persist. This +example only covers a single instance; however, for HA you will want to replicate it to two additional nodes (3 nodes in total). + +## HPE Etcd Setup +1. export HostIP="" +2. Create the hpe-etcd.yaml file below; note that this file shares the TLS settings of your Kubernetes etcd cluster. In production + you should create your own TLS keys and certificates for this separate etcd key value database. +``` +cat < hpe-etcd.yaml +apiVersion: v1 +kind: Pod +metadata: + labels: + component: hpe-etcd + tier: control-plane + name: hpe-etcd + namespace: kube-system +spec: + containers: + - command: + - etcd + - --advertise-client-urls=https://${HostIP}:23790,http://${HostIP}:4001 + - --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt + - --cert-file=/etc/kubernetes/pki/etcd/server.crt + - --key-file=/etc/kubernetes/pki/etcd/server.key + - --client-cert-auth=true + - --data-dir=/var/lib/hpe-etcd + - --initial-advertise-peer-urls=https://${HostIP}:23800 + - --initial-cluster-token=etcd-cluster-1 + - --initial-cluster-state=new + - --initial-cluster=m2-dl360g9-75=https://${HostIP}:23800 + - --listen-client-urls=https://127.0.0.1:23790,https://127.0.0.1:4001 + - --listen-peer-urls=https://${HostIP}:23800 + - --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt + - --peer-client-cert-auth=true + - --peer-key-file=/etc/kubernetes/pki/etcd/peer.key + - --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt + - --snapshot-count=10000 + image: k8s.gcr.io/etcd:3.3.15-0 + imagePullPolicy: IfNotPresent + livenessProbe: + failureThreshold: 8 + httpGet: + host: 127.0.0.1 + path: /health + port: 2381 + scheme: HTTP + initialDelaySeconds: 15 + timeoutSeconds: 15 + name: hpe-etcd + resources: {} + volumeMounts: + - mountPath: /var/lib/hpe-etcd + name: hpe-etcd-data + - mountPath: /etc/kubernetes/pki/etcd + name: etcd-certs + hostNetwork: true + priorityClassName: system-cluster-critical + volumes: + - hostPath: + path: /etc/kubernetes/pki/etcd + type: DirectoryOrCreate + name: etcd-certs + - hostPath: + path: /var/lib/hpe-etcd + type: DirectoryOrCreate + name: hpe-etcd-data +status: {} +EOF +``` From 614c3a8a43f0fdde66feceba32c29b139e8172be Mon Sep 17 00:00:00 2001 From: Shaker Gilbert Date: Tue, 22 Oct 2019 09:57:16 -0400 Subject: [PATCH 3/5] Updated listening addresses to "0.0.0.0" --- docs/example-hpe-etcd.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/example-hpe-etcd.md b/docs/example-hpe-etcd.md index a1c78655..d29941d9 100644 --- a/docs/example-hpe-etcd.md +++ b/docs/example-hpe-etcd.md @@ -3,7 +3,8 @@ After generating the file, place it in the /etc/kubernetes/manifests directory t example only covers a single instance; however, for HA you will want to replicate it to two additional nodes (3 nodes in total). ## HPE Etcd Setup -1. export HostIP="" +1. Set the node IP address for step 2 +```export HostIP=""``` 2. Create the hpe-etcd.yaml file below; note that this file shares the TLS settings of your Kubernetes etcd cluster. In production you should create your own TLS keys and certificates for this separate etcd key value database. ``` @@ -30,8 +31,8 @@ spec: - --initial-cluster-token=etcd-cluster-1 - --initial-cluster-state=new - --initial-cluster=m2-dl360g9-75=https://${HostIP}:23800 - - --listen-client-urls=https://127.0.0.1:23790,https://127.0.0.1:4001 - - --listen-peer-urls=https://${HostIP}:23800 + - --listen-client-urls=https://0.0.0.0:23790,https://0.0.0.0:4001 + - --listen-peer-urls=https://0.0.0.0:23800 - --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt - --peer-client-cert-auth=true - --peer-key-file=/etc/kubernetes/pki/etcd/peer.key From 67b3071c91d2f187372b36f0269050853269c1de Mon Sep 17 00:00:00 2001 From: Shaker Gilbert Date: Tue, 22 Oct 2019 10:01:10 -0400 Subject: [PATCH 4/5] Added example reference to NOTE --- docs/quick_start_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/quick_start_guide.md b/docs/quick_start_guide.md index 7271ece8..02e7a02a 100644 --- a/docs/quick_start_guide.md +++ b/docs/quick_start_guide.md @@ -118,7 +118,7 @@ export HostIP="" ``` 2. Run the following Docker command to create the HPE etcd container ->**NOTE:** etcd stores the HPE 3PAR volume metadata and is required for the plugin to function properly. If you have multiple instances of etcd running on the same Docker node, you will need to modify the default etcd ports (2379, 2380, 4001) and make the adjustment in the **hpe.conf** as well. +>**NOTE:** etcd stores the HPE 3PAR volume metadata and is required for the plugin to function properly. If you have multiple instances of etcd running on the same Docker node, you will need to modify the default etcd ports (2379, 2380, 4001) and make the adjustment in the **hpe.conf** as well. See example [/docs/example-hpe-etcd.md](/docs/example-hpe-etcd.md). ``` sudo docker run -d -v /usr/share/ca-certificates/:/etc/ssl/certs -p 4001:4001 \ From f59b35706d0377a661bef9792ab09969390ea490 Mon Sep 17 00:00:00 2001 From: Shaker Gilbert Date: Tue, 22 Oct 2019 10:03:55 -0400 Subject: [PATCH 5/5] Updated example EOF output The file will now write to /etc/kubernetes/manifests/hpe-etcd.yaml --- docs/example-hpe-etcd.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/example-hpe-etcd.md b/docs/example-hpe-etcd.md index d29941d9..fbb7f7c9 100644 --- a/docs/example-hpe-etcd.md +++ b/docs/example-hpe-etcd.md @@ -8,7 +8,7 @@ example only covers a single instance; however, for HA you will want to replicat 2. Create the hpe-etcd.yaml file below; note that this file shares the TLS settings of your Kubernetes etcd cluster. In production you should create your own TLS keys and certificates for this separate etcd key value database. ``` -cat < hpe-etcd.yaml +cat < /etc/kubernetes/manifests/hpe-etcd.yaml apiVersion: v1 kind: Pod metadata: