Bypass E_CHE_API_NOTFOUND

[gnoejuan]

Is your enhancement related to a problem? Please describe.

It appears the Che deployed an expired certificate.

Describe the solution you'd like

There have been other situations where I wanted to retry an installation of Che, but because the API was non-functional, server:stop and server:delete don't work.

Instead of trying to use an API, perhaps kubectl could be used to undo any changes?

Describe alternatives you've considered

Documentation of CheCtl's internals so the end user could manually undo chectl's action.

Additional context

[tolusha]

@gnoejuan
Do you have any errors with server:delete command?

[gnoejuan]

Yes. I believe my current problem isn't related to Che exactly. Currently I believe the problem is with my k8s deployment, but I'm still hunting that down.

chectl server:start -a helm -b mainhub.lan -p k8s

My browser still says there's a problem with the cert (new private browsing window), but I do see the CLI says 404.

[tolusha]

@gnoejuan
Thank you. I got it.

[SpontaneousDuck]

Perfect, I am also seeing the same issue. I think I am having a different problem with the front end as my browser just throws ERR_CONNECTION_TIMED_OUT but the issue with chectl server:delete is the same. Thanks for looking at this @tolusha

[gnoejuan]

Just to confirm, the certificate problem was/is most likely a problem with k3s.

k3s-io/k3s#1621

I guess, just following up. After migrating back to microk8s, the cert was fine.