• Documentation
  • Tutorials
  • Case studies
  • Blogs
  • Product

What's on this Page

  • Example use cases
    • Mount you company secret into an Pods
    • Add lifecycle hooks to your Pods
    • Install dependencies to your PODs (before startup)
    • Step Controller additional properties
  • Step
  • Set up Step
  • Installation
  • Install in Kubernetes
  • Cloud material
Categories: ADMIN GUIDE CLOUD
This article references one of our previous releases, click here to go to our latest version instead.

Cloud material

Example use cases

Mount you company secret into an Pods

Assuming that a secret called “my-company-secret” is mounted by a K8s administrator in your namespace, you could mount it to your Agents by adding the below in your values file, in the Agent section:

...
extraVolumeMounts:
- mountPath: /home/agent/my-company-secret
  name: my-company-secret
  readOnly: true
extraVolumes:
- name: my-company-secret
  secret:
  secretName: my-company-secret
...

That way, your secret content will be mounted to the Agent(s) at /home/agent/my-company-secret.

Add lifecycle hooks to your Pods

Assuming you would like to perform Agent post start actions, for instance adding a CA cert to a NSSB database store, add the below to your values file, in the Agent section:

...
lifecycleHooks:
  postStart:
    exec:
      command:
      - /bin/bash
      - -c
      - certutil -d /home/agent/.pki/nssdb -N --empty-password && certutil -A -n "My Company Root CA" -t "TCu,Cu,Tu" -i /home/agent/my-company-secret/ca.crt -d sql:/home/agent/.pki/nssdb/
...

Install dependencies to your PODs (before startup)

It is possible to install external dependencies before startup of the Controller or the Agents Pods using the FULL_STEP_DP special property, as per below:

...
  config:
    FULL_STEP_DP: "https://nexus.mycompany.ch/mydependency-1.0.0.zip,https://artifactory.mycompany.ch/myotherdependency-1.0.0.zip"
 ...
  

The dependencies have to be specified as fully qualified URLs, comma separated, without extra spaces.

There are requirements for the dependencies installation:

  • They must be zip archives
  • There must be an “install.sh” file in the archive root -> the “install.sh” script will be executed on the Pods at startup, and can be used to perform various tasks before startup

Step Controller additional properties

It is possible to customize the Step Controller configuration file by appending extra properties, using the config.additionalProperties setting:

...
config:
  additionalProperties:
    cosmetics.folder: /home/controller/data/cosmetics
    cosmetics.interceptedResourceList: step-variables.css,logotopleft.png
    encryption.manager.keypair.folder: /home/controller/data/encryptionmanager
    plugins.EncryptionManagerControllerPlugin.enabled: true
    plugins.PrometheusControllerPlugin.enabled: true
    plugins.jmeter.home: /home/controller/jmeter-5.6.2/apache-jmeter-5.6.2/
    plugins.pdftest.gsexe: /home/controller/ghostscript/bin/ghostscript
    plugins.soapui.home: /home/controller/soapui-5.7.0/SoapUI-5.7.0/
    ...
...

See Also

  • Autoscaler configuration
  • Helm Values
  • Agent configuration for Step SaaS
  • Step Portal
  • Access enterprise artifacts
  • Home
  • Whats new?
  • Set up
    • Requirements
    • Installation
      • Install from archive
      • Install in Kubernetes
        • Cloud material
        • Helm Values
      • Access enterprise artifacts
    • Configuration
  • Administration
  • SaaS guide
  • User guide
  • Developer guide
  • DevOps
  • Plugins
  • Libraries
Step Logo
    • Documentation
    • Tutorials
    • Case studies
    • Blogs
    • Product
    • Home
    • Whats new?
    • Set up
      • Requirements
      • Installation
        • Install from archive
        • Install in Kubernetes
          • Cloud material
          • Helm Values
        • Access enterprise artifacts
      • Configuration
    • Administration
    • SaaS guide
    • User guide
    • Developer guide
    • DevOps
    • Plugins
    • Libraries