-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8s Helm release-2.0.0 CVAT not logging in #4438
Comments
I also have this problem |
Duplicate of #4192 |
As also mentioned in #4192 the current helm charts miss the Open Policy Agent container introduced in cvat 2.0. I am working on a updated helm chart. Maybe I can share it when it is finished. Main problem so far. It will need an additional custom container where opa and the rules are bundled. Mouting those from a local directory will not work with k8s. |
Closed since 2.0 is a too old release. |
My actions before raising this issue
Testing out release on k8s using the helm chart from branch
release-2.0.0
. We already have a working deployment for release-1.7.0. This release deploys ok but once we login to the super user/user it throughs a strage error. perticularly :Expected Behaviour
should be able to log in to the super user without issue
Current Behaviour
Possible Solution
Looking at the git diff and the docker-compose file a seems like a new service was introduced
openpolicyagent/opa
. but i do not see this in the deployment charts or any mention of it any where. could this have been casuse due to this missing service. Also see the logs belowSteps to Reproduce (for bugs)
Context
Was trying to upgrade cvat from 1.7.0 to 2.0.0 on k8s.
Your Environment
Git hash commit (
git log -1
): commit 8aaa450 (HEAD -> release-2.0.0, origin/release-2.0.0)Docker version
docker version
(e.g. Docker 17.0.05): not applicableAre you using Docker Swarm or Kubernetes?: yes. using k8s
Operating System and version (e.g. Linux, Windows, MacOS): Linux, ubunut
Code example or link to GitHub repo or gist to reproduce problem: see above steps to reproduce
Other diagnostic information / logs:
Next steps
You may join our Gitter channel for community support.
The text was updated successfully, but these errors were encountered: