Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

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

ProcessSummary
Orchestrator accessGranting a user access to the Orchestrator API and the Orchestrator UI.
CI accessSetting up a repository so that its GitHub Actions workflows can trigger Known Test Plans.
Private image publishingAllowing 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:

ChangeSummary
GitHub repository accessAllowing the Orchestrator to read Test Plans from a GitHub repository.
Rate limit changesChanging the per-user rate limits for a Workload Pool.
Workload cluster capacityProvisioning or scaling clusters and Workload Pools.
Additional Kubernetes permissionsGranting Scenarios Kubernetes permissions beyond write access to their own namespace.
Toolbox image changesAdding 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.