oke-arc-runners-opentofu
Skill0 starsChanged 8 days agoMITView on GitHub
Use when designing, reviewing, or implementing self-hosted GitHub Actions runners on Oracle Kubernetes Engine with Actions Runner Controller and OpenTofu. Covers runner scale sets, GitHub App secrets, OKE kubeconfig, autoscaling, and declarative rollout boundaries.
In this repository108 other files it gives its agents.
- adaptive-estimationSkill
- adaptive-loop-budgetingSkill
- adopt-and-deleteSkill
- adversarial-reviewSkill
- agent-drives-uiSkill
- agentic-coding-loopSkill
- agent-otel-trajectorySkill
- agents-as-iac-modulesSkill
- ascii-ui-mockupsSkill
- authoring-html-emailSkill
- authoring-skills-vs-mcpSkill
- batched-ssh-enumerationSkill
- c4-architectureSkill
- challenge-the-premiseSkill
- codegraph-bootstrapSkill
- codegraph-worktree-startupSkill
- colocated-pod-tolerationsSkill
- command-creatorSkill
- complexity-budgetsSkill
- connector-readinessSkill
- context-anchored-patchingSkill
- continuous-issue-resolutionSkill
- credential-proxySkill
- criticality-tiered-reportingSkill
- data-connector-buildingSkill
- declarative-firstSkill
- disk-pressure-forensicsSkill
- early-return-over-elseSkill
- email-triageSkill
- enums-codify-behaviorSkill
- ephemeral-workspace-lifecycleSkill
- event-sourcingSkill
- evidence-claim-boundariesSkill
- exhaustive-matchSkill
- feature-coverage-not-just-line-coverageSkill
- full-disk-forensicsSkill
- gate-before-pushSkill
- github-pr-shepherdingSkill
- graceful-shutdown-stateful-agentsSkill
- grounded-generationSkill
- iac-incident-responseSkill
- iac-not-ad-hocSkill
- instrumented-service-scaffoldSkill
- interface-over-conditionalsSkill
- knowledge-routingSkill
- lean-on-oss-standardsSkill
- live-money-disciplineSkill
- live-state-verificationSkill
- loop-governance-and-learningSkill
- low-level-executor-task-specSkill
- map-dispatch-over-conditionalsSkill
- merge-conflict-disciplineSkill
- mermaid-diagramsSkill
- orchestrate-agySkill
- orchestrate-claudeSkill
- orchestrate-codexSkill
- orchestrate-geminiSkill
- otel-emit-at-willSkill
- parameter-designSkill
- parse-dont-validateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for self-hosted GitHub Actions runners on Oracle Kubernetes Engine managed through OpenTofu and GitOps.
- Distinctive: line 15
Prefer the official OKE module where its provider constraints fit the root.
- Distinctive: line 16
If it requires newer provider major versions than the GitOps/bootstrap root, split the stack into a cluster root and a GitOps root instead …
- Distinctive: line 19
Keep runner scale set values in source.
- Distinctive: line 24
Use Actions Runner Controller runner scale sets and listeners, not hand-rolled long-lived runner pods.
- Very specific: line 26
Treat each runnerScaleSetName as unique to one GitHub App installation and one target scope.
- Distinctive: line 29
Put the runner image behind a pinned tag or digest.
- Distinctive: line 31
Use a pull secret for private registry access and keep it synchronized from the secret manager.
- Very specific: line 36
Use a GitHub App credential for ARC's githubConfigSecret:
- Distinctive: line 43
Never print or commit the private key.
- Distinctive: line 63
Before calling the runner substrate ready, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OKE ARC Runners With OpenTofu
Use this skill for self-hosted GitHub Actions runners on Oracle Kubernetes Engine managed through OpenTofu and GitOps.
Source Of Truth
- Declare OKE, node pools, IAM, registry access, and Kubernetes bootstrap in OpenTofu modules and GitOps manifests.
- Prefer the official OKE module where its provider constraints fit the root. If it requires newer provider major versions than the GitOps/bootstrap root, split the stack into a cluster root and a GitOps root instead of forcing one mixed provider graph.
- Keep runner scale set values in source. Do not patch live controller objects to change images, labels, secrets, or scaling.
Runner Scale Sets
- Use Actions Runner Controller runner scale sets and listeners, not hand-rolled long-lived runner pods.
- Treat each
runnerScaleSetNameas unique to one GitHub App installation and one target scope. Active-active failover with the same scale-set name can steal or strand jobs. - Put the runner image behind a pinned tag or digest. The image contract must state whether Docker, rootless BuildKit, or a daemonless builder is present.
- Use a pull secret for private registry access and keep it synchronized from the secret manager.
GitHub App Secret
Use a GitHub App credential for ARC's githubConfigSecret:
app_idinstallation_idprivate_key
Store these in the established secret manager and sync them into Kubernetes. Never print or commit the private key. Preserve PEM bytes exactly when moving the key between systems.
OKE Details
- OKE kubeconfig commonly uses an
ociexec-credential plugin. Every CI, deploy, and verification context that runskubectl,helm, or GitOps health checks must have that plugin onPATHwith the right cloud auth. - OKE Basic clusters may not expose the public OIDC issuer needed by keyless workload identity flows. Verify the issuer before designing a federation flow that depends on it.
- Karpenter is AWS-specific. For OKE burst capacity, use Cluster Autoscaler with an OCI-compatible build and instance-principal or workload-identity access to resize node pools.
- The stock upstream Cluster Autoscaler image may not include the
oci-okecloud provider. Pin an OCI-compatible image and verify it starts withcloudProvider=oci-oke.
Verification
Before calling the runner substrate ready, verify:
- OpenTofu validates and plans the declared resources.
- GitOps syncs the controller, listener, and runner scale set.
- A real workflow job lands on the expected scale set.
- The runner pod uses the intended image digest and can access required build tools.
- Autoscaler can observe pending runner pods and resize the intended node pool.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

