https://github.com/cinnamondoll/dollop

declarative self-hosting on k8s
https://github.com/cinnamondoll/dollop

argocd k0s k8s self-hosted

Last synced: 3 months ago
JSON representation

declarative self-hosting on k8s

• Host: GitHub
• URL: https://github.com/cinnamondoll/dollop
• Owner: cinnamondoll
• Created: 2024-09-05T12:43:28.000Z (4 months ago)
• Default Branch: blend
• Last Pushed: 2024-09-18T21:39:41.000Z (4 months ago)
• Last Synced: 2024-09-27T02:25:42.329Z (4 months ago)
• Topics: argocd, k0s, k8s, self-hosted
• Language: Dockerfile
• Homepage:
• Size: 125 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# dollop

![smudge the table cat lied about k8s just needing a yaml file](smudge-lied.jpg)

This is my self-hosting attempt with k8s. My goals are:

- host public and private things for me and my friends

- spend less time maintaining the boring stuff

- learn k8s

Some of the boring stuff is solved with automation, such as:

- declarative workflow rather than procedural

- [argocd][4] continously checks out this repo and basically runs `kubectl apply --recursive -f manifests` for me

- [renovatebot][5] is monitoring this repo for outdated things and makes pull requests itself

### Wanna help?

Feel free to suggest anything that improves or adds to this setup, just open an issue.

### Forks

If you fork, make sure to also fork [dollop-secrets][1] and make it private.

At the moment you'd have to change a bunch of things after a fork, like [prep/hosts][2], [prep/k0sctl.yml][3], and basically any domain mentioned in `manifests`. I'm sorry about this, I'll think of a way to improve this in the future.

PS use my [updown.io][6] referral, thank you~

[1]: https://github.com/cinnamondoll/dollop-secrets

[2]: prep/hosts

[3]: prep/k0sctl.yml

[4]: https://github.com/argoproj/argo-cd

[5]: https://github.com/renovatebot/renovate

[6]: https://updown.io/r/DnQTP