feat: cli delete command

[Vafilor]

What this PR does:

Adds a basic delete command.

Which issue(s) this PR fixes:

Fixes onepanelio/onepanel#270

Special notes for your reviewer:

This does not wait to see if all resources have been deleted, so it may take the cluster a few seconds to delete everything.

Use in conjunction with: onepanelio/manifests#102

[aleksandrmelnikov]

@Vafilor Wanted to bring this up for consideration.
I deployed with CLI, using "default" for namespace.
During clean-up:

Unable to delete: error when deleting ".onepanel/kubernetes.yaml": namespaces "default" is forbidden: this namespace may not be deleted

Since it wasn't deleted, it's didn't impact the k8s cluster.
I see we use application-system in our manifests, so was this supposed to be cleaned-up as a namespace as well?

• If so, that error may have stopped application-system namespace from being deleted.

Not sure if we should point this out via code, or ignore it via code, or not worry about this error.

[Vafilor]

@Vafilor Wanted to bring this up for consideration.
I deployed with CLI, using "default" for namespace.
During clean-up:

Unable to delete: error when deleting ".onepanel/kubernetes.yaml": namespaces "default" is forbidden: this namespace may not be deleted

Since it wasn't deleted, it's didn't impact the k8s cluster.
I see we use application-system in our manifests, so was this supposed to be cleaned-up as a namespace as well?

• If so, that error may have stopped application-system namespace from being deleted.

Not sure if we should point this out via code, or ignore it via code, or not worry about this error.

@aleksandrmelnikov That's a good point, I didn't consider that case.
It'd be easiest if we didn't allow the default namespace of course. But that might be inconvenient.

What do you think @rushtehrani? Should we not allow default for now, just rework logic so default is allowed?

[rushtehrani]

What do you think @rushtehrani? Should we not allow default for now, just rework logic so default is allowed?

@Vafilor I am good with disallowing default and updating CLI and manifest default and comments accordingly.

[Vafilor]

What do you think @rushtehrani? Should we not allow default for now, just rework logic so default is allowed?

@Vafilor I am good with disallowing default and updating CLI and manifest default and comments accordingly.

Sounds good. How about sample for the new "default" namespace?

[rushtehrani]

Sounds good. How about sample for the new "default" namespace?

I think something like my-project would make more sense. Ideally we make it <namespace> and show an error if they left it as a placeholder.

[Vafilor]

Sounds good. How about sample for the new "default" namespace?

I think something like my-project would make more sense. Ideally we make it <namespace> and show an error if they left it as a placeholder.

<namespace> with error detection is doable. I'll add this to this PR.

[rushtehrani]

@Vafilor added default to reserved ns list here