This article is totally wrong in some many ways, that I'm just dumbfounded. I think this was written by some AI that has no clue about reality.
Allow me to correct just a few points:
1st. China is a latecomer to the project. In fact, while they officially joined, they have very little presence on the build process. There are presently no Chinese teams working along the rest of them on the Observatory.
2nd. SKAMPI is (was) an internal technology to setup an integration ground for the work from the various teams on the SKA Observatory. It was deprecated about 6 months ago, because it was just unmaintainable (the teams were constantly breaking it). I don't understand where they got the name from, because it has absolutely nothing to do with the name. No, the SKA telescopes are not "known as SKAMPI". There was a collaboration known as "SKAMP" though, maybe that was mentioned somewhere, and it all got mixed up.
3rd. The telescopes are located in South Africa and Australia, and the headquarters where we centralise the monitoring and control in the UK.
4th. It's not driven by docker, that's just silly. The build and integration process mostly runs on 2 Kubernetes clusters. The image build process was made in house so that it's mostly automated by GitLab pipelines we created. The teams only have to submit the code, tag a release, and the pipeline builds and publishes all the artefacts for them. The controlling resides at the antennas (in this case for the Mid telescopes) also in a k8s cluster that orchestrates the various services we need.
I'm really appalled at the terrible reporting here.
EDIT: On 2. Seems like this was now adopted. A collab with Max Planck Institute, that was sometimes abbreviated as SKA-MPI, now (as of 24th of January) became SKAMPI (using the same name as the deprecated integration platform).