Skip to content

running 301-statefulset-agent-to-run-k8s-jobs-using-ai-job /9.0.20.200 step 3, CCM hosts didn't add #76

@deathhoung

Description

@deathhoung

Folloing 301, I have finish to generate a image for Control-M/Agent.
while running the step 3 : "kubectl apply -f stateful_ha.yaml"

persistentvolumeclaim/ha-agent-pvc unchanged
statefulset.apps/ha-statefulset-agent unchanged

The messages as below:

[controlm@km ~]$ kubectl get all

NAME READY STATUS RESTARTS AGE
pod/web-app01-7b6d698dc6-4ktxj 1/1 Running 0 134m
pod/web-app01-7b6d698dc6-6n6mj 1/1 Running 0 134m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP 10.96.0.1 443/TCP 3d
service/web-app01 NodePort 10.105.40.208 80:30469/TCP 3d

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/web-app01 2/2 2 2 3d

NAME DESIRED CURRENT READY AGE
replicaset.apps/web-app01-7b6d698dc6 2 2 2 3d

NAME READY AGE
statefulset.apps/ha-statefulset-agent 0/2 65m

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions