Caddy as a whole architecture consideration for k8s

[goodwill]

1. The problem I’m having:

I wanna understand if my primary web service architecture is based on k8s, how should I consider to fit caddy in? The whole automatic https feature looks amazing, but I think I need a way to understand the entire fit in given caddy seems not designed to be running on k8s as a primary deployment scenario just yet.

2. Error messages and/or full log output:

N/A

3. Caddy version:

N/A

4. How I installed and ran Caddy:

a. System environment:

Kubernetes (Google Cloud)

[francislavoie]

You could use GitHub - caddyserver/ingress: WIP Caddy 2 ingress controller for Kubernetes which is community maintained. It doesn’t unlock Caddy’s full potential, but it’s one way to have an ingress proxy with Caddy’s automated certs.

[goodwill]

My concern is if the ingress is not an official offering this will have a lot of upgrade hiccups, so I am kinda asking more about large use cases who used caddy together with k8s what is the usual deployment approach?