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
* 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
To uninstall/delete the `my-release` deployment:
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.
> **Tip** > The Portworx configuration files under `/etc/pwx/` directory are preserved, and will not be deleted.
## **Limitations**
* The portworx helm chart can only be deployed in the kube-system namespace. Hence use "kube-system" in the "Target namespace" during configuration.
```
helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
## **Uninstalling the Chart**
#### You can uninstall Portworx using one of the following methods:
#### **1. Delete all the Kubernetes components associated with the chart and the release.**
## Installing the Chart using the CLI
> **Note** > The Portworx configuration files under `/etc/pwx/` directory are preserved, and will not be deleted.
To install the chart with the release name `my-release` run the following commands substituting relevant values for your setup:
To perform this operation simply delete the application from the Apps page
##### NOTE:
`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
#### **2. Wipe your Portworx installation**
> **Note** > The commands in this section are disruptive and will lead to data loss. Please use caution..
See more details [here](https://2.1.docs.portworx.com/portworx-install-with-kubernetes/install-px-helm/#uninstall)
`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.
See the installation details [here](https://2.1.docs.portworx.com/cloud-references/auto-disk-provisioning/aws)
Error: no available release name found
```
This most likely indicates that Tiller doesn't have the right RBAC permissions.
You can verify the tiller logs
```
[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
```
## ** 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
#### Helm install errors with "Job failed: BackoffLimitExceeded"
* Create Kubernetes secret
* 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.
Ensure the correct etcd URL is set as a parameter to the `helm install` command.
#### Helm install errors with "Job failed: Deadline exceeded"
* 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.
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
Follow the below steps to check the reason for failure.
```
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.
drives:none# NOTE: This is a ";" seperated list of drives. For eg: "/dev/sda;/dev/sdb;/dev/sdc" Defaults to use -A switch.
usefileSystemDrive:false# true/false Instructs PX to use an unmounted Drive even if it has a filesystem.
usedrivesAndPartitions:false# Defaults to false. Change to true and PX will use unmounted drives and partitions.
journalDevice:
kvdb:
ownEtcdOption:none
etcdAuth:none
etcdType:none# KVDB type
kvdb:"etcd:http://192.168.70.90:2379"
internalKVDB:false# internal KVDB
etcd:
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
...
...
@@ -13,13 +11,11 @@ etcd:
key:none# Name of certificate key for ETCD authentication Should be server.key
consul:
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>
managementInterface:none# Name of the interface <ethX>
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.
platformOptions:none# AKS, EKS or GKE platforms
customRegistryURL:
registrySecret:
...
...
@@ -28,12 +24,12 @@ clusterName: mycluster # This is the default. please change it to
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
stork:true# Use Stork https://docs.portworx.com/scheduler/kubernetes/stork.html for hyperconvergence.
storkVersion:2.1.0
storkVersion:2.2.5
lighthouse:true
lighthouseVersion:2.0.3
lighthouseSyncVersion:0.3
lighthouseStorkConnectorVersion:0.1
lighthouseVersion:2.0.5
lighthouseSyncVersion:2.0.5
lighthouseStorkConnectorVersion:2.0.5
deployOnMaster:false# For POC only
csi:false# Enable CSI
...
...
@@ -45,4 +41,113 @@ serviceAccount:
deploymentType:oci# accepts "oci" or "docker"
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)