SKAO environments reference

This reference lists the SKAO datacentre identifiers and deployment environment types documented across the developer portal.

Datacentre identifiers

CI/CD datacentres

Identifier	Scope	Purpose
stfc-techops	Central CI/CD	Development, integration, staging, and shared CI/CD workloads.
stfc-dp	Central data processing	CI/CD and data-processing workloads.
aws-cicd	AWS CI/CD	Replacement CI/CD platform used while STFC is unavailable.

ITF and production datacentres

Identifier	Scope	Purpose
mid-itf	Mid telescope	Mid Integration and Test Facility.
low-itf	Low telescope	Low Integration and Test Facility.
mid-aa	Mid telescope	Mid Array Assembly environment.
low-aa	Low telescope	Low Array Assembly environment.
psi-mid	Mid telescope	Mid integration environment at PSI.
psi-low	Low telescope	Low integration environment at PSI.
digital-signal-psi	Digital signal processing	Digital-signal integration environment at PSI.
aws-*	AWS	Several AWS-hosted production environments. They run telescope tools such as OSO, and CI/CD services such as Validations, Marvin MR, Vault, and Harbor.

Deployment environment types

Type	Namespace	Purpose
development	ci-dev-<project>	Short-lived environment for branch deployments and development testing.
integration	integration-<project>	Persistent environment for testing changes from the main branch.
staging	staging-<project>	Persistent environment for validating tagged release candidates.
production	Set by the platform owner	Operational environment with restricted deployment and debugging access.

The templates repository provides the deployment job for each type and sets these names. Use Environment naming conventions to see the namespace and GitLab environment each template creates.

CI/CD VPNs

Platform	Datacentre identifier	Network access
TechOps	stfc-techops	TechOps VPN profile supplied by the System Team.
DP	stfc-dp	Separate DP VPN profile. A TechOps profile does not provide access.

Request either profile from the System Team, and production VPN access from the #team-bang Slack channel. Both profiles are requested and used the same way, as described in Configure your development environment.

Clusters that publish no endpoint, including the ITF and Array Assembly environments, are reached through InfraHQ rather than a VPN. See Access a cluster with InfraHQ.

Related references

Use Reference to find logging identifiers and service URLs. Use Deploy to SKAO environments to configure deployments to SKAO Kubernetes clusters. Use Configure your development environment to configure CI/CD VPN access.

Note

SKAO infrastructure evolves. If a product pipeline uses an identifier that is not listed here, use the runner and environment configuration from that pipeline and contact the System Team to confirm the current name.