Skip to content

update index.md text and gce diagram #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tarrow wants to merge 1 commit into
base: main
Choose a base branch
from
Open

update index.md text and gce diagram #92

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1,266 changes: 0 additions & 1,266 deletions diagrams/2021-tech-overview-gce-k8s.drawio.svg
View file
Open in desktop

This file was deleted.

4 changes: 4 additions & 0 deletions diagrams/2026-tech-overview-gce-k8s.drawio.svg
View file
Open in desktop

@outdooracorn outdooracorn Aug 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the images aren't loading in the full-screen view of this for me (e.g. mariadb, argocd, helmfile), but they do in the small preview, so I assume it's okay.

@outdooracorn outdooracorn Aug 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 3-way-ish arrow between the mediawiki group, the api-backend, and the query-gateway is confusing to me. Looking at the "From API" text and a little bit of domain knowledge, I'm assuming that the query-gateway calls the api-backend and the fact it is touching the mediawiki group to api-backend line means nothing? However, this was present in the original diagram, so I won't block this PR.

@outdooracorn outdooracorn Aug 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The platform-nginx now calls the api-backend in order to route to mediawiki. Should this be on the diagram?

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 7 additions & 3 deletions tech/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,16 +8,20 @@ You can read about this decision [here](/docs/tech/decisions/0000-gce-vs-other-k

The only current deployment of this stack is [wikibase.cloud](https://wikibase.cloud).

![](./../diagrams/2021-tech-overview-gce-k8s.drawio.svg)
![](./../diagrams/2026-tech-overview-gce-k8s.drawio.svg)

@addshore addshore Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mentioned elsewhere, but it might be neat to first move the diagram to a file name such as tech-overview-gce-k8s.drawio.svg
And then change it from there in antoehr commit, so that the github diff image visualization can be used to see the differences

@outdooracorn outdooracorn Aug 20, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! I would like this, but I won't block merging by requiring it's done.


# Code & Config

All code lives on Github in the [wbstack org](https://github.com/wbstack).
All code lives on Github in the [wbstack org](https://github.com/wbstack) or the [wmde org](https://github.com/wmde)

@addshore addshore Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the point of view of "wbstack" the software that can deploy multiple wikibases via the k8s seutp, i beleive "all code" still lives on github?
Only the wmde wikibase.cloud deployment repo i believe is on the wmde org?
So perhaps just linking to that deploy repo makes sense?

And or link to a specific filtered list of repos on the wmde org if there are indeed more

@tarrow tarrow Aug 20, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given how rarely this is updated I'm not keen to enumerate what appears to be en exhaustive list which is then likely to get out of date.

I believe there are 3 vaguely relevant repos in the wmde org:

  • wmde/wbaas-deploy
  • wmde/wbaas-backup
  • wmde/wikibase-cloud-status (no code that really lands in the cluster)


Github Actions are used in code repositories for testing and building of containers.

Wikibase.cloud deployment is managed by a [public deploy git repository](https://github.com/wmde/wbaas-deploy). This includes Terraform/OpenTofu code and configuration for kubernetes tooling.

## Historic

The wbstack.com deployment was managed in the [deploy git repository](https://github.com/wbstack/deploy).

A private git repository is used alongside this to provide secret infomation to the deployments.
A private git repository was used alongside this to provide secret infomation to the deployments.

![](./../diagrams/2021-tech-overview-develop-deploy.drawio.svg)
Loading