This helm chart deploys [Portworx](https://portworx.com/) and [Stork](https://docs.portworx.com/scheduler/kubernetes/stork.html) on your Kubernetes cluster. The minimum requirements for deploying the helm chart are as follows:
Use this Helm chart to deploy [Portworx](https://portworx.com/) and [Stork](https://docs.portworx.com/scheduler/kubernetes/stork.html) to your Kubernetes cluster.
- All [Pre-requisites](https://docs.portworx.com/scheduler/kubernetes/install.html#prerequisites) for Portworx must be fulfilled.
Prerequisites
## Limitations
Refer to the [Install Portworx on Kubernetes via Helm](https://docs.portworx.com/portworx-install-with-kubernetes/install-px-helm/#pre-requisites) page for the list of prerequisites.
## **Limitations**
* The portworx helm chart can only be deployed in the kube-system namespace. Hence use "kube-system" in the "Target namespace" during configuration.
* The portworx helm chart can only be deployed in the kube-system namespace. Hence use "kube-system" in the "Target namespace" during configuration.
* You can only deploy one portworx helm chart per Kubernetes cluster.
## Uninstalling the Chart
## **Uninstalling the Chart**
To uninstall/delete the `my-release` deployment:
#### You can uninstall Portworx using one of the following methods:
> **Tip** > The Portworx configuration files under `/etc/pwx/` directory are preserved, and will not be deleted.
#### **1. Delete all the Kubernetes components associated with the chart and the release.**
```
> **Note** > The Portworx configuration files under `/etc/pwx/` directory are preserved, and will not be deleted.
helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
To perform this operation simply delete the application from the Apps page
`kvdb` is a required field. The chart installation would not proceed unless this option is provided.
If the etcdcluster being used is a secured ETCD (SSL/TLS) then please follow instructions to create a kubernetes secret with the certs. https://docs.portworx.com/scheduler/kubernetes/etcd-certs-using-secrets.html#create-kubernetes-secret
See the installation details [here](https://2.1.docs.portworx.com/portworx-install-with-kubernetes/install-px-helm/)
`clusterName` should be a unique name identifying your Portworx cluster. The default value is `mycluster`, but it is suggested to update it with your naming scheme.
## **Installing Portworx on AWS**
See the installation details [here](https://2.1.docs.portworx.com/cloud-references/auto-disk-provisioning/aws)
Example of using the helm CLI to install the chart:
## ** Giving your etcd certificates to Portworx using Kubernetes Secrets.**
```
This is the recommended way of providing etcd certificates, as the certificates will be automatically available to the new nodes joining the cluster
* Copy all your etcd certificates and key in a directory etcd-secrets/ to create a Kubernetes secret from it. Make sure the file names are the same as you gave above.
#### Helm install errors with "no available release name found"
This most likely indicates that Tiller doesn't have the right RBAC permissions.
# ls -1 etcd-secrets/
You can verify the tiller logs
etcd-ca.crt
etcd.crt
etcd.key
```
```
[storage/driver] 2018/02/07 06:00:13 get: failed to get "singing-bison.v1": configmaps "singing-bison.v1" is forbidden: User "system:serviceaccount:kube-system:default" cannot get configmaps in the namespace "kube-system"
[tiller] 2018/02/07 06:00:13 info: generated name singing-bison is taken. Searching again.
[tiller] 2018/02/07 06:00:13 warning: No available release names found after 5 tries
[tiller] 2018/02/07 06:00:13 failed install prepare step: no available release name found
```
#### Helm install errors with "Job failed: BackoffLimitExceeded"
* Use kubectl to create the secret named px-etcd-certs from the above files:
Verifying if the provided etcd url is accessible: http://192.168.70.179:2379
Response Code: 000
Incorrect ETCD URL provided. It is either not reachable or is incorrect...
```
```
Ensure the correct etcd URL is set as a parameter to the `helm install` command.
* Notice that the secret has 3 keys etcd-ca.crt, etcd.crt and etcd.key, corresponding to file names in the etcd-secrets folder. We will use these keys in the Portworx spec file to reference the certificates.
#### Helm install errors with "Job failed: Deadline exceeded"
This error indicates that the pre-install hook for the helm chart has failed to run to completion correctly. Verify that the etcd URL is accessible. This error occurs on kubernetes cluster(s) with version below 1.8
etcd-ca.crt: 1679 bytes
Follow the below steps to check the reason for failure.
etcd.crt: 1680 bytes
etcd.key: 414 bytes
```
kubectl get pods -nkube-system -a | grep preinstall
[Portworx](https://portworx.com/) is a software defined persistent storage solution designed and purpose built for applications deployed as containers, via container orchestrators such as Kubernetes, Marathon and Swarm. It is a clustered block storage solution and provides a Cloud-Native layer from which containerized stateful applications programmatically consume block, file and object storage services directly through the scheduler.
[Portworx](https://portworx.com/) is a software defined storage overlay that allows you to
* Run containerized stateful applications that are highly-available (HA) across multiple nodes, cloud instances, regions, data centers or even clouds
* Migrate workflows between multiple clusters running across same or hybrid clouds
* Run hyperconverged workloads where the data resides on the same host as the applications
* Have programmatic control on your storage resources
# Please uncomment and specify values for these options as per your requirements.
# Please uncomment and specify values for these options as per your requirements.
drives:none# NOTE: This is a ";" seperated list of drives. For eg: "/dev/sda;/dev/sdb;/dev/sdc" Defaults to use -A switch.
kvdb:
usefileSystemDrive:false# true/false Instructs PX to use an unmounted Drive even if it has a filesystem.
ownEtcdOption:none
usedrivesAndPartitions:false# Defaults to false. Change to true and PX will use unmounted drives and partitions.
etcdAuth:none
journalDevice:
etcdType:none# KVDB type
kvdb:"etcd:http://192.168.70.90:2379"
internalKVDB:false# internal KVDB
etcd:
etcd:
credentials:none:none# Username and password for ETCD authentication in the form user:password
credentials:none:none# Username and password for ETCD authentication in the form user:password
ca:none# Name of CA file for ETCD authentication. server.ca
ca:none# Name of CA file for ETCD authentication. server.ca
cert:none# Name of certificate for ETCD authentication. Should be server.crt
cert:none# Name of certificate for ETCD authentication. Should be server.crt
key:none# Name of certificate key for ETCD authentication Should be server.key
key:none# Name of certificate key for ETCD authentication Should be server.key
consul:
consul:
token:none# ACL token value used for Consul authentication. (example: 398073a8-5091-4d9c-871a-bbbeb030d1f6)
token:none# ACL token value used for Consul authentication. (example: 398073a8-5091-4d9c-871a-bbbeb030d1f6)
region:none# US or EU regions for Portworx hosted etcds
dataInterface:none# Name of the interface <ethX>
dataInterface:none# Name of the interface <ethX>
managementInterface:none# Name of the interface <ethX>
managementInterface:none# Name of the interface <ethX>
platformOptions:none# AKS, EKS or GKE platforms
isTargetOSCoreOS:false# Is your target OS CoreOS? Defaults to false.
pksInstall:false# installation on PKS (Pivotal Container Service)
AKSorEKSInstall:false# installation on AKS or EKS.
customRegistryURL:
customRegistryURL:
registrySecret:
registrySecret:
...
@@ -28,14 +24,14 @@ clusterName: mycluster # This is the default. please change it to
...
@@ -28,14 +24,14 @@ clusterName: mycluster # This is the default. please change it to
secretType:k8s# Defaults to None, but can be AWS / KVDB / Vault.
secretType:k8s# Defaults to None, but can be AWS / KVDB / Vault.
envVars:none# NOTE: This is a ";" seperated list of environment variables. For eg: MYENV1=myvalue1;MYENV2=myvalue2
envVars:none# NOTE: This is a ";" seperated list of environment variables. For eg: MYENV1=myvalue1;MYENV2=myvalue2
stork:true# Use Stork https://docs.portworx.com/scheduler/kubernetes/stork.html for hyperconvergence.
stork:true# Use Stork https://docs.portworx.com/scheduler/kubernetes/stork.html for hyperconvergence.
storkVersion:2.1.0
storkVersion:2.2.5
lighthouse:true
lighthouse:true
lighthouseVersion:2.0.3
lighthouseVersion:2.0.5
lighthouseSyncVersion:0.3
lighthouseSyncVersion:2.0.5
lighthouseStorkConnectorVersion:0.1
lighthouseStorkConnectorVersion:2.0.5
deployOnMaster:false# For POC only
deployOnMaster:false# For POC only
csi:false# Enable CSI
csi:false# Enable CSI
serviceAccount:
serviceAccount:
...
@@ -43,6 +39,115 @@ serviceAccount:
...
@@ -43,6 +39,115 @@ serviceAccount:
create:true
create:true
name:
name:
deploymentType:oci# accepts "oci" or "docker"
deploymentType:oci# accepts "oci" or "docker"
imageType:none#
imageType:none#
imageVersion:2.0.3.3# Version of the PX Image.
imageVersion:2.1.5# Version of the PX Image.
result:none
environment:none
onpremStorage:none
maxStorageNodes:none
journalDevice:none
usefileSystemDrive:false# true/false Instructs PX to use an unmounted Drive even if it has a filesystem.
usedrivesAndPartitions:false# Use unmounted disks even if they have a partition or filesystem on it. PX will never use a drive or partition that is mounted. (useDrivesAndPartitions)