agentleFS
selamy-labsselamy-labs/agent-skills/skills/oke-arc-runners-opentofu/SKILL.md

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.

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
  1. Distinctive:

    Use this skill for self-hosted GitHub Actions runners on Oracle Kubernetes Engine managed through OpenTofu and GitOps.

    line 8
  2. Distinctive:

    Prefer the official OKE module where its provider constraints fit the root.

    line 15
  3. Distinctive:

    If it requires newer provider major versions than the GitOps/bootstrap root, split the stack into a cluster root and a GitOps root instead …

    line 16
  4. Distinctive:

    Keep runner scale set values in source.

    line 19
  5. Distinctive:

    Use Actions Runner Controller runner scale sets and listeners, not hand-rolled long-lived runner pods.

    line 24
  6. Very specific:

    Treat each runnerScaleSetName as unique to one GitHub App installation and one target scope.

    line 26
  7. Distinctive:

    Put the runner image behind a pinned tag or digest.

    line 29
  8. Distinctive:

    Use a pull secret for private registry access and keep it synchronized from the secret manager.

    line 31
  9. Very specific:

    Use a GitHub App credential for ARC's githubConfigSecret:

    line 36
  10. Distinctive:

    Never print or commit the private key.

    line 43
  11. Distinctive:

    Before calling the runner substrate ready, verify:

    line 63

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 runnerScaleSetName as 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_id
  • installation_id
  • private_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 oci exec-credential plugin. Every CI, deploy, and verification context that runs kubectl, helm, or GitOps health checks must have that plugin on PATH with 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-oke cloud provider. Pin an OCI-compatible image and verify it starts with cloudProvider=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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.