Steps I took to install this to kubernetes
See original GitHub issueI had some issues deploying this to kubernetes, so to at least try to document my steps for the next person, this is what I did:
- Add a standard deployment, define your mounts/PVC’s as you normally do. Add init as an argument to the container, such as:
containers:
- name: archivebox
args: ["init"]
image: archivebox/archivebox
(If you mount a block-device, using for example Rook, as your PVC, you’ll have a Lost+Found-folder in /data - archivebox will not do the init-phase then, I used a sleep-container (davralin/sleep), exec’ed into it and removed lost+found)
- After the initial run, change init to server, like so:
containers:
- name: archivebox
args: ["server"]
image: archivebox/archivebox
(dont forget to reapply with kubectl) 3. Exec into the container, and drop to archivebox’s dedicated user, like so:
su -l archivebox -s /bin/bash
This allows you to manage the installation, using archivebox add or whatever.
I used archivebox manage createsuperuser
to create a user, and then do the rest from the web-page.
This is the steps I did to deploy AB to my kubernetes-cluster, put the docs somewhere you think it’s appropriate. 😃
Let me know if I should add the manifests I used for the deployment anywhere.
The init-part was the hardest to be honest, because the container exists immediately when started - some kind of configuration-options (using env) for doing the initial init (and ignoring lost+found) would be much appreciated for the next person. (Could probably be done by an init-container, but I’m not there yet)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top GitHub Comments
Nice, so with those changes in place, this is my relevant manifest:
Now who can pass up free Github credits… 😃