Orchestrator internal processes
Note: This page describes Apollo internal processes. Concrete details are maintained in internal Confluence documentation linked below.
Some Orchestrator functionality depends on setup or configuration that only the Runtime Readiness team or an Orchestrator admin can provide. This page summarizes each of the internal processes involved and links to the documentation that describes how to follow them.
Access
| Process | Summary |
|---|---|
| Orchestrator access | Granting a user access to the Orchestrator API and the Orchestrator UI. |
| CI access | Setting up a repository so that its GitHub Actions workflows can trigger Known Test Plans. |
| Private image publishing | Allowing a repository to publish Docker images to Apollo’s internal registry for Test Plans. |
Orchestrator configuration
Rate limits, Workload Pools, and cluster configuration are set in the
Orchestrator configuration file. To request a change, start a conversation in
#proj-runtime-testing-framework. If the change is going to go forward, raise a Jira ticket in
the RR backlog to track it.
This process covers changes such as:
| Change | Summary |
|---|---|
| GitHub repository access | Allowing the Orchestrator to read Test Plans from a GitHub repository. |
| Rate limit changes | Changing the per-user rate limits for a Workload Pool. |
| Workload cluster capacity | Provisioning or scaling clusters and Workload Pools. |
| Additional Kubernetes permissions | Granting Scenarios Kubernetes permissions beyond write access to their own namespace. |
| Toolbox image changes | Adding tools to the image used to run Test Executions. |
Bugs and feature requests
Report bugs and request new Orchestrator functionality in #proj-runtime-testing-framework.