BCDevOps / devops-requests

This repository is used to track the DevOps requests for platform services team.
18 stars 11 forks source link

Please remove the Capstone project namespace set from the Pathfinder cluster #1014

Closed jleach closed 3 years ago

jleach commented 3 years ago

Step 0

Are you the Product Owner or Technical Lead? Yes

If you are one of these two people, please ensure that you also request Openshift access if you don't have it already. This request does NOT grant you access to the platform itself - you will find a separate request for that on the issues page of this repo!

However, you may submit both requests at the same time - there's no need to wait until that request has been completed to submit this one.

Have you migrated all workloads including production from the OCP 3.11 namespaces to the OCP 4 Silver cluster? Yes

Have you scaled down all pods to 0 in all 4 project set namespaces - dev, test, tools and prod ? Yes

Have you deleted the persistent volume claims in all 4 project set namespaces - dev, test, tools and prod ? Yes

Step 1

Make sure no duplicated request exists, search here: https://github.com/BCDevOps/devops-requests/issues

Confirmed

Step 2

Confirm that you are aware that you are requesting to:

Remove a project set **Note: There is no rollback or restore of the deployments once a namespace is deleted.

Step 3

Please provide the names of the namespaces to be deleted in the form of a 6 character alphanumeric code followed by the environment, like so: a1b2c3-prod.

xordpe-dev CITZ IMB Capstone 2020 Playbook Exemplar (dev) Active xordpe-prod CITZ IMB Capstone 2020 Playbook Exemplar (prod) Active xordpe-test CITZ IMB Capstone 2020 Playbook Exemplar (test) Active xordpe-tools CITZ IMB Capstone 2020 Playbook Exemplar (tools) Active

Thanks!

requestron[bot] commented 3 years ago

This issue has now been closed. It has been completed, unless a comment indicates otherwise.

Assuming this request has been approved, your 3.11 project set has now been deleted. Congratulations on your migration to Openshift 4!

If you have additional problems or questions, please feel free to ask the community on RocketChat on the #devops-howto channel!