This file can also be downloaded from the following location: 

env: - name: ADMIN_PASSWORD valueFrom: secretKeyRef: key: password name: icp-mongodb-admin volumeMounts: - mountPath: "/backup" name: backup - mountPath: "/ca" name: cluster-ca - mountPath: "/certs" name: mongodb-certs tolerations: - effect: NoSchedule key: dedicated operator: Exists volumes: - name: backup persistentVolumeClaim: claimName: core-backup - name: cluster-ca secret: secretName: cluster-ca-cert - name: mongodb-certs secret: secretName: icp-mongodb-client-cert - name: etcd-certs secret: secretName: etcd-secret restartPolicy: Never 

https://github.com/IBMRedbooks/SG248440-IBM-Cloud-Private-System-Administrator- s-Guide/tree/master/Ch3-Backup-and-Restore/Backup/core-backup_cronjob.yaml 

2. The ETCD-ENDPOINT  environment variable for the etcd container should be changed to reflect an actual etcd IP address. Modify the containers section in Example 3-4 and replace #ETCD-ENDPOINT with an appropriate etcd IP address. 

containers: - name: etcddump image: ibmcom/etcd:3.2.24 command: ["/bin/sh","-c","cat /certs/etcd-cert > client.pem; cat /certs/etcd-key > client-key.pem; cat /certs/etcd-ca > ca.pem; etcdctl --cert=client.pem --key=client-key.pem --cacert=ca.pem --endpoints https://$(ENDPOINT):4001 snapshot save /data/etcd.$(date +%Y-%m-%d_%H:%M:%S).db"] env: - name: ENDPOINT value: "#ETCD-ENDPOINT" 

3. Alternatively, sed  can be used to easily do this, by executing sed -i -e s/#ETCD-ENDPOINT/<etcd-endpoint>/g core-backup_cronjob.yaml  replacing <etcd-endpoint>  with your own. 

