Yeah...so in India, the GLP patent owners went to court. however, it was deemed as patent expired in March 2026.

In anycase, India generally doesnt honor product patents for pharma. Right now, Indian pharma cos are court empowered to churn out GLP-1.

Everyone knows that we are gonna have 10$ GLP-1 before 2027 coming out of India.

That's why the major Indian generics companies like Cipla have signed IP and branding exclusivity deals with Lilly and Novo so that they can continue to synthesize generic GLPs but Lilly and Novo can now export those to the US - it allows IP holders in the US to further enhancing margins while allowing Indian generics manufacturers to climb up the value chain thanks to transferred IP and knowhow.

docker != docker compose.

docker compose is just as heavy. there's not a significant difference between k3s and docker compose.

this is OpenClaw's docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos... . Arguably the hottest thing in the world right now. Mac Minis are out of stock because of this.

At no point, have I invented a new/better method. Perhaps your way is better.

I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default. And it isnt going away, no matter hard anyone tries to kill. Some things are just too well designed. Docker Compose is one of those things.

I'm just making it possible to run those on kubernetes seamlessly.

this is OpenClaw's docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos...

I'm not arguing for the relative superiority of jsonnet vs yaml vs anything else. I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default.

I'm just making it possible to run those on kubernetes seamlessly.

hey thanks so much !

just curious - i actually didnt focus on healthcheck because i wasnt sure if anyone was using it. are you using it for local dev ?

docker compose is beautiful because it uses a simple elegant compose yml file - this is now an open standard. https://www.compose-spec.io/

the standard does not make it mandatory that underlying system should be docker compose (the reference server). it can be anything.

IMHO - kappal is the first project that takes your compose yml file and transparently/drop-in runs it on kubernetes. there is nothing extra you need. It is useful for people who want to maintain their stack as close to production as possible (kubernetes).

If that's not a big goal for you, then this is not very useful for you. But I'd argue ...why do you care if the compose yml is the only think you are using. you get all of kubernetes.

the test folder is for a large real project that i test on (and actually use in real life myself). it has a deliberate gitignore. plenty of tests in https://github.com/sandys/kappal/tree/main/testdata and https://github.com/sandys/kappal/tree/main/scripts

fair. however, i do genuinely find docker compose yml and dev-experience to be much more pleasant and intuitive.

if you ever wanna try it again - use kappal. you will get a full k8s but with the UX of docker compose.

yes. fixing this right now. you will have it in a day or two.

Would certainly try this out!

this is done. Please feel free to try that.

Also, btw - kappal is architected AI first. Meaning: 1. we have a beautiful skill that can be used by Claude 2. The help command generates output that is useful for claude 3. we have a "kappal inspect" command that generates live output of the stack that can be used by Claude.

hope you have a great time using it. Please file bugs!

Might take a couple of days until I have time to try, but certainly will!

This is a personal project that im open-sourcing. Its one of those projects-that-should-exist-but-nobody-wants-to-kill-their-business.

It takes ur standard docker compose file and runs it transparently in kubernetes (k3s actually). So ur devs don't have cognitive dissonance between testing ur stack locally on ur laptop and making it work on kubernetes in production.

It is primarily meant as a dev tool on ur laptop, and as a replacement for docker compose.

Compare/contrast with kubedock? It is almost exactly same project as your description from what I can tell

kubedock is its own command set. it doesnt work with compose.yml . This project specifically starts with a compose file.

NOTE: kubedock has some automatic compatibility with compose, this is not their goal - https://github.com/joyrex2001/kubedock/blob/e4c8540f63d65e33...

If you are not on the compose ecosystem, this is isnt useful to you.

Just fyi - the hottest thing in the world right now is OpenClaw. This is OpenClaw docker compose yml - https://github.com/openclaw/openclaw/blob/main/docker-compos...

even if you dont do docker compose....everyone else does it anyway.