When you update an existing Engineering Lifecycle Management instance configuration, you
must start the Engineering Lifecycle Management application pods to reflect the changes. Use the following procedure to start the application pod by using the Red Hat® OpenShift® or Kubernetes CLI method. It helps you to start the application pods of selected Engineering Lifecycle Management
applications or all applications in the Engineering Lifecycle Management instance.
Procedure
- Log in to the Red Hat OpenShift or Kubernetes cluster by using CLI.
- Draft a YAML configuration to start the application pods with a name
start-all-apps.yaml
apiVersion: elm.ibm.com/v1
kind: ELMOperation
metadata:
name: start-all-apps
labels:
app.kubernetes.io/instance: ibm-elm-operator
app.kubernetes.io/managed-by: Go
app.kubernetes.io/name: ibm-elm-operator
release: 1.0.0
namespace: example-namespace
spec:
selectedApplications:
ccm: false
dcc: false
gc: false
jas: false
rb: false
jts: false
ldx: false
lqe: false
qm: false
eni: false
rm: false
allApplications: true
operationType: startApplicationPod
In the example before,
operationType must be set as
startApplicationPod.
Note: If you want to start only specific applications, add the
flag as true for all respective applications. If you want to start all
applications, set allApplications as true
- Create an ELMOperation instance to start the application pods.
For Red Hat OpenShift, use the following command
oc create -f start-all-apps.yaml
For Kubernetes, use the following command
kubectl create -f start-all-apps.yaml
- The ELMOperation gets created and appears in the list. To verify the successful creation
ELMOperation instance
For Red Hat
OpenShift, use the following command
oc get ELMOperation -n example-namespace
For Kubernetes, use the following command
kubectl get ELMOperation -n example-namespace