I was able to get this working in VSCode using a php unit test plugin that allows one to define a command to exec into docker. I used kubectl exec command for this: kubectl exec -it deploy/mediawiki-default

My only concern would be scope creep as far as making what was agreed at techconf to be a simple solution in mw/core to something much bigger, but after re-reading I understand this as a separate project that could be used in conjunction with a docker-compose environment.

Determined that portals is the only thing requiring the jessie permanent instance after discussion with @thcipriani. If we can get a container to build portals we can move off of the permanent instance.

Closing since we will build the image manually for now.

Closing since we decided to keep the restbase chart in local-charts after all. See T228915.

Closing due to parsoid soon becoming a library pulled into core. No parsoid image or helm chart will be necessary.

Restrouter is no longer in k8s in production and according to https://phabricator.wikimedia.org/T242461 might go away. Until that happens, we decided to keep the restbase chart in local-charts and update it to restrouter due to being able to merge and iterate more quickly.

I attempted to run puppet with the role role::ci::slave::labs on an instance I created, integration-slave-test-jeena. I got the following errors:

@Dzahn Thanks for the response. So parsoid is using a standalone daemon, right?

@ssastry Can you help clarify how to use the new php version of Parsoid? We have a docker image and helm chart for the JS version and want to update our containerized environment to reflect the changes made to Parsoid. Is there a php parsoid service or is all that is necessary to enable it on mediawiki/core? I'm having a bit of trouble finding documentation.

Thanks @mobrovac!

I think the hotfix still needs to be merged to 1.35.0-wmf.2 https://gerrit.wikimedia.org/r/c/mediawiki/core/+/543730

@josephine_l I'll volunteer to lead or co-lead this session and T235372.

Here is some existing work we (Releng) have done on the local development environment recently:

you need to downgrade your minikube to version 1.3
If using homebrew, you can do it by installing a link to the old file. I found the commit on github.
so I think you need to do the following:

brew cask uninstall minikube
brew cask install https://raw.githubusercontent.com/Homebrew/homebrew-cask/210a0d0c3d8dcd555985092c756e17f721828328/Casks/minikube.rb

I've deleted my instance so it shouldn't be cluttering the logs anymore.

@Krenair I wasn't able to run puppet because of the ferm problem you mentioned. @thcipriani commented out ferm.conf and was able to run puppet as far as I know.

Hi Phaebz, thanks for testing out the windows install! How is the documentation going?

This is being done as part of migrating our charts to the deployment-charts repo