Trouble with kubernetes
-
Hi,
I’m trying to get kopano working on kubernetes, I used https://github.com/Kopano-dev as a guide.
I first translated the docker compose files to a docker only config, this configuration works. Then I converted the containers to several pods on kubernetes. The only difference being that the names of the containers are replaced with service names, which are all resolvable, and accessible from within the containers.
accessing https://kopano.demo/webapp gives a login page, but after logging in to the web page, I get an empty page (with only the kopano default background image).
I searched all the logs, but the only thing i could find was:
webapp + web containers: “POST /webapp/kopano.php?service=token HTTP/1.1” 401 (unauthorized)
this is the only error i get in the logs of all the containers.anybody any idea as to where this goes wrong? or where to look?
-
Hi @allthesenames,
as part of our prof services we are currently developing helm charts for Kopano. I’d recommend to reach out to our support if you have a subscription to request access to these.
Without knowing the exact versions and logging it can only be a guess, but when webapp stays at the login background (and if you are using openid connect to signin) then the reason could be that there is no store for the user.
-
@fbartels said in Trouble with kubernetes:
Without knowing the exact versions and logging it can only be a guess, but when webapp stays at the login background (and if you are using ope
Thanks for the answer, I will try to get those helm charts.
But in the meantime, what do you mean no user store?
openid is configured in the same way in k8s as it is in a working docker configuration. with the demo ldap container. According to the ldap container logs, the user gets authenticated. Konnectd logging is configured on info level. But there are no errors, or any other notifications after: ready to handle requests.Konnectd version: 0.29.0
kopano version: 10.0.1
kopano-webapp version: 4.0.2652 -
@allthesenames said in Trouble with kubernetes:
what do you mean no user store?
With the LDAP backend there is a separate process between user creation and store creation. there was a bug with the master build, where stores were not created. Maybe that is what you’re seeing.
-
If there were no user store, the login would be rejected with a red nondescript text “Cannot connect to Kopano Core.”, rather than just showing a background.
