Add ability to delete pre-existing resources about airshipctl

[alanmeadows]

One decision we’ll need to make on this feature is how to determine what those resources are. One idea is to ensure any resource airshipctl creates is tagged with a special annotation set to determine not only what is owned by airshipctl in general (useful for delete-all) but also at what phase it was applied, e.g. init infra. This should make delete operations rather simplistic as it would just find all resources in the cluster matching these two annotations.

[ianpittwood]

I'll take a stab at this

[ianpittwood]

I started on a change here https://review.opendev.org/#/c/707472/

I think I have some questions though. It seems like creating CRUD operations for each type of resource might be a tedious way to approach this, but that seems to be the method that K8s go-client lays out for us. There are third party libraries like this that implement some extra layers of abstraction to allow us to reference resources via string instead of type objects. We could also leverage kubectl to delete resources, but that might be a messy way to go about doing this. Does anyone have any thoughts of how we can cleanly implement this functionality to meet our goals?

[airshipbot]

Related Change #707472

Subject: [WIP][#8] Implement ability to delete existing resource
Link: https://review.opendev.org/c/airship/airshipctl/+/707472
Status: ABANDONED
Owner: Ian Pittwood ([email protected])

Approvals

Code-Review
! None
Verified
-1 Zuul
Workflow
! None

Last Updated: 2021-03-19 12:39:17 CDT

Issue reopened due to new activity on Gerrit.

[jezogwza]

Will open a new issue to discuss leveraging pruning as a mechanism from controlled deletions.

[eak13]

Closing due to being reopened by abandoned patchset