Understanding Kubernetes based Container Deployment Process

After you have completed the prerequisite tasks, you are ready to deploy IBM Sterling External Authentication Server. Before you begin consider the following:

A Helm chart is organized as a collection of files inside a directory by the name of the Chart itself. For more information see, Helm Charts.
Example Helm Chart
```
<Name of a Chart/> 
  Chart.yaml          # A YAML file containing information about the Chart.
  LICENSE             # OPTIONAL: A plain text file containing the license for the Chart.
  README.md           # OPTIONAL: A README file.
  requirements.yaml   # OPTIONAL: A YAML file listing dependencies for the Chart.
  values.yaml         # The default configuration values for this Chart.
  Charts/             # A directory containing any Charts upon which this Chart depends.
  templates/          # A directory of templates that, when combined with values, generates valid Kubernetes manifest files.
  templates/NOTES.txt # OPTIONAL: A plain text file containing short usage notes.
```
- This Helm chart deploys IBM Sterling External Authentication Server on a container management platform with the following resource deployments:
  - A statefulset pod <release-name>-ibm-seas with 1 replica
  - A configMap <release-name>-ibm-seas. This is used to provide default configuration in seas_config_file.
  - A service <release-name>-ibm-seas. This is used to expose the SEAS services for accessing using clients.
  - A service-account <release-name>-ibm-seas-serviceaccount. This service will not be created if serviceAccount.create is `false`

Kubernetes Based Container Software commands
1. To install a Chart
```
$ helm install
```
2. To upgrade to a new release
```
$ helm upgrade
```
3. To rollback a release to a previous version
```
$ helm rollback
```
4. To delete the release from Kubernetes.
```
$ helm uninstall
```