Starter profile configuration

You can deploy a starter profile for smaller production workloads, for development, or for simple testing. The starter profile uses less CPU and memory from the Red Hat® OpenShift® cluster compared to the production profile because it does not configure multiple replicas of the underlying services.

For sizing information about the starter profile, see Sizing requirements.

Deploy the following configuration to create a starter profile of WebSphere Automation that includes both server health and security monitoring components.

apiVersion: automation.websphere.ibm.com/v1
kind: WebSphereAutomation
metadata:
   name: wsa
spec:
  replicas: 1
  dataStore:
    replicas: 1
  license:
    accept: true
  events:
    broker:
      replicas: 1
      resources:
        limits:
          cpu: '1'
          memory: 1Gi
        requests:
          cpu: '1'
          memory: 1Gi
      storage:
        size: 10Gi
    controller:
      replicas: 1
      resources:
        limits:
          cpu: '1'
          memory: 1Gi
        requests:
          cpu: '1'
          memory: 1Gi
      storage:
        size: 2Gi
---
apiVersion: automation.websphere.ibm.com/v1
kind: WebSphereSecure
metadata:
  name: wsa-secure
spec:
  license:
    accept: true
  replicas: 1
---
apiVersion: automation.websphere.ibm.com/v1
kind: WebSphereHealth
metadata:
  name: wsa-health
spec:
  license:
    accept: true
  replicas: 1

To deploy a starter profile that includes security monitoring only, omit the WebSphereHealth portion from the configuration.