Installing

Edit online

After you review the system requirements and other planning information, you install IBM Container Software for Sterling Secure Proxy by completing the pre- installation tasks and installation process. 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.
  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 Secure Proxy Configuration Manager on a container management platform with the following resource deployments:
  - A statefulset pod <release-name>-ibm-ssp-cm-0 1 replica by default.
  - A configMap <release-name>-ibm-ssp-cm. This is used to provide default configuration in cm_config_file.
  - A service <release-name>-ibm-ssp-cm. This is used to expose the CM services for accessing using clients.
  - A service-account <release-name>-ibm-ssp-cm-serviceaccount. This service will not be created if `serviceAccount.create` is `false`.
  - A persistence volume claim <release-name>-ibm-ssp-cm
- This Helm chart deploys IBM Sterling Secure Proxy Engine on a container management platform with the following resource deployments:
  - A statefulset pod <release-name>-ibm-ssp-engine-0 1 replica by default.
  - A configMap <release-name>-ibm-ssp-engine. This is used to provide default configuration in engine_config_file.
  - A service <release-name>-ibm-ssp-engine. This is used to expose the engine services for accessing using clients.
  - A service-account <release-name>-ibm-ssp-engine-serviceaccount. This service will not be created if `serviceAccount.create` is `false`.
  - A persistence volume claim <release-name>-ibm-ssp-engine
- This Helm chart deploys IBM Sterling Secure Proxy Perimeter Server on a container management platform with the following resource deployments:
  - A statefulset pod <release-name>-ibm-ssp-ps-0 1 replica by default.
  - A configMap <release-name>-ibm-ssp-ps. This is used to provide default configuration in ps_config_file.
  - A service <release-name>-ibm-ssp-ps. This is used to expose the Perimeter Server services for accessing using clients.
  - A service-account <release-name>-ibm-ssp-ps-serviceaccount. This service will not be created if `serviceAccount.create` is `false`.

Container Software commands:
For more information on other commands and options, see Helm 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
```
$ helm uninstall
```