agentleFS
G1JoshiG1Joshi/Agent-Skills/skills/devops/linode/SKILL.md

linode

Skill15 starsChanged 42 days agoMITView on GitHub

Expert Akamai Linode cloud assistance covering Compute Instances, NodeBalancers, Block Storage, LKE (Kubernetes), and CLI automation. Use when deploying cost-effective Linux cloud infrastructure.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use root passwords for instances.

    line 154

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Linode (Akamai Connected Cloud)

Akamai Connected Cloud (formerly Linode) provides developer-friendly cloud compute, object storage, and edge networking for deploying distributed, low-latency workloads.

When to Use

  • Cost-Effective Cloud Compute (Akamai Cloud): Reliable, straightforward Linux virtual machines (Nanodes to High-Memory instances).
  • Linode Kubernetes Engine (LKE): Fully managed Kubernetes clusters with zero control-plane fee.
  • NodeBalancers & Object Storage: Highly available layer 4/7 load balancers and S3-compatible bucket storage.
  • Akamai Global Edge Integration: Combining compute with Akamai CDN and edge security services.

Quick Start

# Configure Linode CLI
linode-cli configure

# Create Linode 2GB instance with Ubuntu 24.04
linode-cli linodes create \
  --type g6-standard-1 \
  --region us-east \
  --image linode/ubuntu24.04 \
  --label web-server-01 \
  --root_pass "$ROOT_PASSWORD"

Core Concepts

Infrastructure as Code with Terraform (Linode Provider)

Deploying a Linode instance with private networking:

terraform {
  required_providers {
    linode = {
      source  = "linode/linode"
      version = "~> 2.15"
    }
  }
}

provider "linode" {
  token = var.linode_token
}

resource "linode_instance" "web_node" {
  label           = "production-web-01"
  image           = "linode/ubuntu24.04"
  region          = "us-east"
  type            = "g6-standard-2"
  authorized_keys = [var.ssh_public_key]
  tags            = ["production", "web"]

  private_ip = true
}

resource "linode_firewall" "web_firewall" {
  label = "web-node-firewall"

  inbound {
    label    = "allow-https"
    action   = "ACCEPT"
    protocol = "TCP"
    ports    = "443"
    ipv4     = ["0.0.0.0/0"]
  }

  inbound {
    label    = "allow-ssh"
    action   = "ACCEPT"
    protocol = "TCP"
    ports    = "22"
    ipv4     = ["198.51.100.0/24"] # Trusted office VPN only
  }

  inbound_policy  = "DROP"
  outbound_policy = "ACCEPT"
  linodes         = [linode_instance.web_node.id]
}

Linode Kubernetes Engine (LKE) Provisioning via CLI

Creating an autoscaling Kubernetes cluster:

# Authenticate Linode CLI
linode-cli configure

# Create a managed LKE cluster
linode-cli lke cluster-create \
  --label prod-cluster \
  --region us-east \
  --k8s_version 1.30 \
  --node_pools.type g6-standard-2 \
  --node_pools.count 3 \
  --node_pools.autoscaler.enabled true \
  --node_pools.autoscaler.min 3 \
  --node_pools.autoscaler.max 8

NodeBalancer Configuration for High Availability

Distributing traffic across backend nodes:

# Create NodeBalancer and HTTPS port 443 configuration
linode-cli nodebalancers create --region us-east --label prod-lb
linode-cli nodebalancers config-create <NB_ID> \
  --port 443 --protocol https --ssl_cert "$CERT" --ssl_key "$KEY" \
  --check http --check_path /healthz --check_interval 10

Common Patterns

NodeBalancer with SSL Termination

Problem: Distributing traffic across multiple compute instances with high availability and SSL offloading.

Solution: Configure Linode NodeBalancer via CLI:

# Create NodeBalancer
NB_ID=$(linode-cli nodebalancers create --region us-east --label app-balancer --json | jq '.[0].id')

# Add HTTPS port 443 configuration
linode-cli nodebalancers configs-create $NB_ID \
  --port 443 \
  --protocol https \
  --ssl_cert "$CERT_PEM" \
  --ssl_key "$KEY_PEM" \
  --check_path "/health"

Best Practices

Do:

  • Attach a Cloud Firewall to all Linode instances; drop all unsolicited inbound traffic by default.
  • Enable private_ip = true and use Linode VPC for private inter-node communication.
  • Leverage LKE (Linode Kubernetes Engine) for production containers; control planes are completely free.
  • Store automated database and system backups using Linode Backup Service or Object Storage.

Don't:

  • Expose SSH (port 22) publicly to 0.0.0.0/0; restrict to known IP ranges or a bastion host.
  • Use root passwords for instances; always inject authorized SSH keys during provisioning.
  • Hardcode Linode API tokens in source code; supply via LINODE_TOKEN environment variable.

Troubleshooting

ErrorCauseSolution
Authentication failed / Token invalidExpired or incorrect Linode personal access token.Re-generate token in Cloud Manager and run linode-cli configure.
Cannot connect to instance via SSHRoot password not set or instance still in booting/provisioning state.Monitor job state with linode-cli linodes list until status is running.
Disk space full on root volumeLogs or temp files filling small standard disk allocation.Resize disk volume in Cloud Manager or attach Linode Block Storage.

References

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.