-
Notifications
You must be signed in to change notification settings - Fork 188
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
WIP: Add proof of concept kubernetes support #1399
base: edge
Are you sure you want to change the base?
Conversation
Thanks again for submitting this @geoah! Starting to take a look here. Tagging @crkrenn, who was mentioning wanting to work on container orchestration (autoscaling, etc); This seems like a great start! And coincidentally, I feel like part of what is missing here is better orchestrated handling of credentials and configuration, which I think connects to challenges with #1341. Thanks again. |
Hello @geoah, I am not very experienced with kubernetes but I was able to set up an instance by following the steps in the README. I couldn't figure out though how to update any of the docker images once I deployed it. The only way I could get changes I made to apply was to run The other issue I ran into was when I tried to vote on a test conversation I created, it would always fail with the alert "Apologies, your vote failed to send. Please check your connection and try again". Here is more info on the error from the response to the POST to http://polis.local/api/v3/votes:
I couldn't figure out the exact cause of this error but when I ran this with |
Thanks so much for trying this out @pmc30! I believe the error you're getting there is related to one of the configuration parameters being missing from the kubernetes configuration. As I mentioned in my previous post, I think most of the remaining work associated with this issue is getting the configuration story situated, so this is not terribly surprising. I think the steps to fixing this involve going through the configuration options in the #1341 and ensuring that they're all reflected in the kubernetes configuration. Thanks again |
This seems to be needed until the following TODO is resolved: https://github.com/compdemocracy/polis/blob/9a294140bbfc50d5bbb50ce4e474f4ad72541881/server/src/session.ts#L8-L10
Hey @pmc30 sorry for missing this, I hadn't subscribed to the notifications for this PR; I'll fix that. A couple of comments on your issue and the kubernetes stuff in general.
I've pushed a commit to add this env var to the server which should resolve this error.
|
Hey @geoah , do you have any updates on this? |
I was able to get this up and running last night, i rebased @geoah's branch to the latest Screen.Recording.2024-11-22.at.7.14.08.PM.mov |
I've opened this PR for a more up to date version of this PR. Since i see it was last active in 2022. |
@metasoarous this is a very basic POC just to get a feel on the direction you are hoping for.
The instructions in the README should result in a hopefully working instance of polis without email support.
I need to figure out how to run tests against this.
Warning: This is work in progress and should not be used in production.
Under the manifests folder you can find a first version of polis running under Kubernetes. It uses an in-cluster postegres as a stateful set, with a persistent volume claim, and exposes the polis server using the cluster's ingress.