Sheogorath

I added a new repository under https://github.com/hackmdio/codimd-container This is the first step. For now we will stay with the current docker repository, moving away from it, will come soon, too...

I consider to provide a commit that will break updates, yes. Basically removing the whole repository content. Except for a note pointing to the new one

Also check out our guides about enabling authentication: https://github.com/hackmdio/codimd/tree/master/docs/guides/auth

Check the URL parameter. Usually it's something with the return url because `CMD_DOMAIN` is not set correctly.

It would probably be better to drop the explicit definition of the image pull policy and let the Kubernetes mutation webhook do its magic for the image tags.

Do you see the `system-upgrade-controller` role in the namespace?

There should be two clusterroles and one role. When I adjusted the roles for the controller, I decided to limit secrets and job creation to the namespace of the controller....

If you apply the release manifest a second time (now that the namespace exists), does it fix the issue?

If you use the manifests directory from the tag in the git repository, you have to apply all manifests. The release manifest I referred to is attached to the Release...

Well, now we know, that #296 actually fixed a problem 🙌🏻