Talk:Core Platform Team/Initiatives/MediaWiki on Kubernetes

There are three main uses of MW on K8S:

1. Developer environment. Making it easier for developers to spin up a reasonable copy of our production environment.
2. Continuous integration. Making it easier to make integration tests for our full stack (MW + Redis + Memcached + replicated MySQL + Kafka + Wikidata + ...)
3. Production. When you point your browser at https://en.wikipedia.org/, the MW you hit is running in K8S.

If we're doing the last one, it's a big question whether all the components (Redis, etc.) get K8S-ized, or just MW.

Are there any performance penalties from running MW in K8S? For example, do all the compiler caching optimisations in PHP still work?

There are a number of existing Docker images. Are we building off of those, or starting from scratch?

...and will we be releasing the output of this project as a Helm chart?

Why are product teams a stakeholder? Is this going to help with having a standardized developer environment?

What are the asterisks for?