As our first step, we will deploy a staging environment for Wikibase.Cloud to wikibase.dev using existing components (incl. MW 1.35). The primary purpose of this staging environment is not product acceptance testing of Wikibase features.

Other considerations
Region
Must be EU-based. After a quick glance europe-west3 seems like it would make the most sense out of the box (Frankfurt).

Kubernetes Namespaces
Right now the wbstack.com deployment only has a single “default” namespace in use.
We can either decide to 1) deploy testing and production to different k8s clusters entirely or 2) deploy them to the same cluster in 2 different namespaces. Current thinking is that option 2 (different namespaces) is best. This will require more changes to charts potentially, probably a “production” and a “test” would suffice. Some services, such as cert-manager and ingress should probably remain in a separate namespace etc.

Domains
We got wikibase.dev for this purpose
PM & Tech Lead have discussed the following proposed structure:

• wikibase.dev & www.wikibase.dev = Dashboard for user wiki creation
• *.wikibase.dev = each individual wiki

Acceptance Criteria

• Developers have an environment that is like production, that they feel comfortable making changes to prior to production. The environment can be used to test technical changes.