- PHP
- Apache
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T198901 Migrate production services to kubernetes using the pipeline | |||
| Open | None | T238770 Deploy MediaWiki to Wikimedia production in containers | |||
| Open | None | T238771 Get production MW-land images built and published | |||
| Open | None | T238773 Create initial production MW-land images with blubber | |||
| Open | None | T238747 Migrate www.wikimedia.org (the portal) to be hosted as a service | |||
| Open | None | T238774 Provide the official production base images for Wikimedia use | |||
| Resolved | Joe | T265324 Create the base container images for running MediaWiki in a production environment | |||
| Open | None | T265876 Logging options for apache httpd in k8s |
Event Timeline
Comment Actions
This task is generic enough, in this form, that I'm not sure wether it's a good idea.
What should this base image set up? A LAMP application (generically)? What other LAMP stack apps we have apart from mediawiki?
If this is specific for MediaWiki usage, then we can cut a few corners and i.e. install the php extensions we feel we need.
Comment Actions
This is a task representing the requirement from you that all images the pipeline builds for MW are based on images you provide. :-)
I agree, it currently doesn't have any specifications, mostly because I feel that it's not for RelEng to tell SRE and Security what outcome you'd be happy with.
What should this base image set up? A LAMP application (generically)? What other LAMP stack apps we have apart from mediawiki?
My understanding was that this wasn't decided. One possibility was that containerised MediaWiki would run on a PHP-only container, with Apache running on a different, isolated container in the same pod. Another was to lump them together.
If this is specific for MediaWiki usage, then we can cut a few corners and i.e. install the php extensions we feel we need.
[Wikimedia usage]? Yes.