okteto destroy gets an error if namespace is already deleted

[phoenix-bjoern]

okteto destroy gets an error if namespace is already deleted

[jLopezbarb]

Hi @phoenix-bjoern, Have you tried using okteto namespace delete?

okteto namespace delete provides a safe way for a user to remove completely a namespace he is owner of without having access to another cluster member namespace.

[phoenix-bjoern]

@jLopezbarb Sure: "This command is only available in clusters where Okteto is installed."
But maybe it a good enhancement to make it configurable in the destroy section to also remove the entire namespace. That way it is not necessary to have a separate command and delete the namespace either via Okteto (server) or "kubectl delete ns" like we do.

[jLopezbarb]

But maybe it a good enhancement to make it configurable in the destroy section to also remove the entire namespace.

I think this is a good feature. I will pass this statement to our product team and plan it accordingly

In order to address your issue. Do you have okteto installed in your cluster? It seems you are using directly the vanilla context. You'll have to run okteto context use $OTKETO_URL + okteto namespace delete in order to make it work. If you don't have okteto installed you should check that the user "u-xyz" indeed has the appropriate permissions and modify your RBAC Rules in order to make the users be able to list configmaps

[phoenix-bjoern]

@jLopezbarb Actually we are not running Okteto in the K8S cluster, we are only using the CLI tool.
Since the issue is not blocking us we don't need a workaround for now. If there is solution in a future release this would be wonderful.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days

[phoenix-bjoern]

Issue still exists.

[jLopezbarb]

Hi @phoenix-bjoern, We didn't have enough capacity to tackle this, but we'll try to address it during the following weeks

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days

[phoenix-bjoern]

@jLopezbarb can you add a flag to this issue to prevent automatic closing?

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days