Apps#

Prerequisites#

export GIT_PATH="$HOME/git/"
export ZONE_NAME="..."
export INFRA_ZONE_NAME="infra-..."

Warning

During this procedure, several steps require restarts of different components in cloud zones. Before each restart:

check there is no CAASCHR that is planned on the same component at the same time
warn supervsion team on #supervision about the component/zone that is going to be restarted

On karma production or staging, create a silence for postgres-backup

Select Alertmanager infra-stg or infra-prd
Set label name = pipeline and set label values = postgres-backup
Set label name = exported_job and set label values = backup-$SERVICE_NAME-$ZONE-TO-DESTROY
Set a duration (2 days should be sufficient)

To delete concourse-workers use trackbone destroy:

FEAWSAzure

trackbone destroy -z "${ZONE_NAME}" -c fe_concourse_workers_client

trackbone destroy -z "${ZONE_NAME}" -c aws_concourse_workers_client

trackbone destroy -z "${ZONE_NAME}" -c azure_concourse_workers_client

Verify the proper execution and destruction all of resources in Kubernetes.

kubectl delete namespace concourse

To delete concourse-workers use trackbone destroy:

FEAWSAzure

trackbone destroy -z "${ZONE_NAME}" -c fe_concourse_workers_infra

trackbone destroy -z "${ZONE_NAME}" -c aws_concourse_workers_infra

trackbone destroy -z "${ZONE_NAME}" -c azure_concourse_workers_infra

Verify the proper execution and destruction all of resources in Kubernetes.

kubectl delete namespace concourse-infra

kubectl delete namespace quay

kubectl delete namespace clair

kubectl delete namespace gitea
kubectl -n velero delete schedule/gitea-daily-schedule

It is possible to have zone-specific configurations in envs-ng which have to be removed.

In the envs-ng repo:

grep -r "${ZONE_NAME}" *.cue # only in files managed by Apps team

If some files were found,