I’m interested in running #FrankenPHP (i.e., #Caddy) as the app server for a website. The website has multiple domains pointing to it, and I plan to run this in a #Kubernetes cluster. Can someone point to any docs or blog posts that show how others have set up similar configurations with Caddy or FrankenPHP, especially with regard to how Caddy magically configures HTTPS for the domains in this kind of setup?
Another option is to let your existing ingress controller do the TLS termination (you can use projects cert-manager to automatically manage the certificates, and many cloud ingresses also have native support Let’s Enctypt or automatic cert generation).
Doe je iets met #opensource, #openstandards of #opensystems dan moet je erbij zijn. In november heb je weer een kans, want we organiseren 2x
p/jr een conferentie.
We zijn een vereniging, dus je kan lid worden! Zie: https://nluug.nl
Having to recycle your #kubernetes nodes because the #HPA isn't scaling up your #Mastodon#sidekiq so you're now lagging 15K jobs behind looks like this in the #UI:
Ok ok I admit that I recycled my nodes because I could. Kicking the pod probably also would have fixed it but they where up for 82 days and it felt fun
Had fun this weekend working on a performance focussed proof of concept using Bunny in the #PHP#queue interop contracts. The first metrics are in using the #RabbitMQ cluster on my #Raspberrypi#Kubernetes home cluster. (Which isn't meant for high performance. Still pleased by these numbers.)
#AlpineLinux is generally my default goto for #kubernetes#container image bases when I'm writing stuff from scratch. I love how lightweight and simple it is, so I'll often start there until I can prove that I need something more complex.
On that note - need to move some #Kubernetes data to S3? Here's an #Alpine image I pushed today that includes #s3cmd and zip and gets built/tested/pushed weekly by our Jenkins farm at my $DAYJOB. Perfect for a sidecar container or CronJob backup, etc. Enjoy! (And if this is useful to you, thank the Alpine and s3cmd folks, because they by far did most of the work.)
@alessandrolai Like when creating a deployment. It tells it to record the command used to create the deployment. If you don’t use it, then it doesn’t record the command, so if you update your deployment and don’t tell it to record, then when you look at your history, you see each revision, but not the command that made the revision.
@ramsey I always only did kubectl apply for changes, never delved deeper so I didn't know this option! I switched to Helm that handles revisions automatically for rollbacks too...
Decided to sit down and try to learn #kubernetes despite the fact that I don't have any real need for it on my little home server. Still, it's been interesting and - I won't lie - a bit frustrating at times. It's very much like using a chainsaw to butter my bread for my use case, but I had a nice feeling of satisfaction when I succeeded in getting #owncast set up through it. I've had some odd issues with Docker failing to launch certain containers through containerd that I have not been able to figure out, however.
I was putting thought into maybe redoing my server setup with kubernetes but I sincerely worry that I'll run into this same containerd issue with some of my other apps.
@jay podman's a "replacement" for docker. The commands are essentially the same as you can do podman build, podman run, etc., just like docker build, etc. ( https://docs.podman.io/en/latest/Commands.html ) Some have symlinked docker -> podman to get scripts to just work. The "k8s" part is that you can feed a k8s-style yaml file (with some types of resources like pods and volumes) to podman play kube ( https://docs.podman.io/en/v4.2/markdown/podman-play-kube.1.html ) and it'll run the container on the local system (like kubectl apply).