You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

Difference between revisions of "Kubernetes/Clusters"

From Wikitech-static
Jump to navigation Jump to search
imported>Legoktm
(→‎staging: TLS is auto-setup)
 
imported>Elukey
Line 13: Line 13:
== staging-codfw ==
== staging-codfw ==
<code>staging-codfw</code> is intended for SREs to adjust and test the configuration of Kubernetes itself.
<code>staging-codfw</code> is intended for SREs to adjust and test the configuration of Kubernetes itself.
== ml-serve-eqiad & ml-serve-codfw ==
These clusters run the Kubeflow Kfserving stack and they are aimed (as first goal) to replace the ORES infrastructure that serves revision scores.

Revision as of 06:15, 2 September 2021

We have multiple Kubernetes clusters deployed in "production".

eqiad & codfw

eqiad and codfw are the primary Kubernetes clusters and serve real traffic. It is expected that most services are deployed identically in both in an active/active fashion.

staging

staging, also known as staging-eqiad, allows developers to deploy and test new versions of their project without affecting user traffic. Typically deployments will only have 1 replica in staging since it has less resources.

In addition, TLS is automatically configured for all services deployed here.

staging-codfw

staging-codfw is intended for SREs to adjust and test the configuration of Kubernetes itself.

ml-serve-eqiad & ml-serve-codfw

These clusters run the Kubeflow Kfserving stack and they are aimed (as first goal) to replace the ORES infrastructure that serves revision scores.