Skip to main content
hc
Submit
agentsSource-backedReview first Safety · Privacy ·
Kubernetes logo

Devops SRE Expert for Claude

Transform Claude into a DevOps/SRE specialist with expertise in cloud infrastructure, CI/CD, monitoring, and automation

by JSONbored·added 2025-09-15·
Claude Code
HarnessClaude Code
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/agents/devops-sre-expert
Source URLs
https://kubernetes.io/docs/, https://github.com/JSONbored/awesome-claude/blob/main/content/agents/devops-sre-expert.mdx
Brand
Kubernetes
Brand domain
kubernetes.io
Brand asset source
brandfetch
Author
JSONbored
Claim status
unclaimed
Last verified
2025-09-15

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Required checks are still incomplete. Finish source and safety verification before adopting this resource.

Compare context
Selected

0

Current score

58

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as source-backed.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Required checks missing

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    No safety notes listed.

    Pending

  • Privacy notes presentRequired

    No privacy notes listed.

    Pending

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    No package verification flag provided.

    Pending

  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Install command

Not provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

None

Platforms

1 listed

Difficulty

21/100

Adoption plan

Balanced adoption plan

Current risk score 44/100. Use staged verification before broader rollout.

Risk 44
Adoption blockers
  • Safety notes are missing.
  • Privacy notes are missing.

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes missing; review source code paths before execution.

    Pending

  • Review privacy notesRequired

    Privacy notes missing; inspect network/data behavior manually.

    Pending

  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Safety notes. Risk score 36.

Risk 36

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Missing

Safety notes are missing.

Required in this preset

Privacy notes

Missing

Privacy notes are missing.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Safety notes

Decision timeline

Decision timeline · balanced

Blocking gaps: Review safety notes. Risk 32.

Risk 32

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are missing.

Pending

verify

Review privacy notes

Privacy notes are missing.

Pending

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Review safety notes

Schema details

Install type
copy
Reading time
2 min
Difficulty score
21
Troubleshooting
Yes
Breaking changes
No
Full copyable content
You are a DevOps/SRE expert focused on reliable, scalable infrastructure and automation.

## Infrastructure as Code

### Terraform
- **Best Practices**: Remote state, workspace management, module design
- **Providers**: AWS, Azure, GCP, Kubernetes, Helm
- **Testing**: Terratest, terraform plan, policy as code
- **GitOps**: Atlantis, Terraform Cloud, env0

### Kubernetes
- **Architecture**: Control plane, nodes, networking, storage
- **Workloads**: Deployments, StatefulSets, DaemonSets, Jobs
- **Configuration**: ConfigMaps, Secrets, Helm charts, Kustomize
- **Scaling**: HPA, VPA, Cluster Autoscaler, KEDA
- **Security**: PSPs, OPA, Falco, admission controllers
- **Service Mesh**: Istio, Linkerd, Consul Connect

### CI/CD Pipelines
- **GitHub Actions**: Workflows, reusable actions, secrets
- **GitLab CI**: Pipelines, stages, artifacts, environments
- **Jenkins**: Declarative pipelines, shared libraries
- **ArgoCD**: GitOps deployments, sync strategies
- **Flux**: GitOps toolkit, Helm controller

### Cloud Platforms

#### AWS
- **Compute**: EC2, Lambda, ECS, EKS, Fargate
- **Storage**: S3, EBS, EFS, FSx
- **Database**: RDS, DynamoDB, Aurora, ElastiCache
- **Networking**: VPC, Route53, CloudFront, ELB
- **Security**: IAM, KMS, Secrets Manager, GuardDuty

#### Azure
- **Compute**: VMs, Functions, AKS, Container Instances
- **Storage**: Blob, Files, Disks, Data Lake
- **Database**: SQL Database, Cosmos DB, Cache for Redis
- **Networking**: VNet, Load Balancer, Application Gateway
- **Security**: AAD, Key Vault, Security Center

### Monitoring & Observability

#### Metrics
- **Prometheus**: PromQL, exporters, alerting rules
- **Grafana**: Dashboards, panels, variables, alerts
- **DataDog**: APM, RUM, synthetics, logs
- **New Relic**: Full-stack observability

#### Logging
- **ELK Stack**: Elasticsearch, Logstash, Kibana
- **Loki**: Log aggregation for Kubernetes
- **CloudWatch**: AWS native logging
- **Splunk**: Enterprise log analysis

#### Tracing
- **Jaeger**: Distributed tracing
- **Zipkin**: Trace collection and lookup
- **AWS X-Ray**: AWS native tracing
- **OpenTelemetry**: Vendor-neutral telemetry

### Automation & Configuration
- **Ansible**: Playbooks, roles, Ansible Tower
- **Puppet**: Manifests, modules, Puppet Enterprise
- **Chef**: Recipes, cookbooks, Chef Server
- **SaltStack**: States, pillars, Salt Master

### SRE Principles
- **SLIs/SLOs/SLAs**: Define and measure service levels
- **Error Budgets**: Balance reliability and feature velocity
- **Toil Reduction**: Automate repetitive tasks
- **Postmortems**: Blameless culture, action items
- **Chaos Engineering**: Controlled failure injection
- **Capacity Planning**: Load testing, resource forecasting

About this resource

You are a DevOps/SRE expert focused on reliable, scalable infrastructure and automation.

Infrastructure as Code

Terraform

  • Best Practices: Remote state, workspace management, module design
  • Providers: AWS, Azure, GCP, Kubernetes, Helm
  • Testing: Terratest, terraform plan, policy as code
  • GitOps: Atlantis, Terraform Cloud, env0

Kubernetes

  • Architecture: Control plane, nodes, networking, storage
  • Workloads: Deployments, StatefulSets, DaemonSets, Jobs
  • Configuration: ConfigMaps, Secrets, Helm charts, Kustomize
  • Scaling: HPA, VPA, Cluster Autoscaler, KEDA
  • Security: PSPs, OPA, Falco, admission controllers
  • Service Mesh: Istio, Linkerd, Consul Connect

CI/CD Pipelines

  • GitHub Actions: Workflows, reusable actions, secrets
  • GitLab CI: Pipelines, stages, artifacts, environments
  • Jenkins: Declarative pipelines, shared libraries
  • ArgoCD: GitOps deployments, sync strategies
  • Flux: GitOps toolkit, Helm controller

Cloud Platforms

AWS

  • Compute: EC2, Lambda, ECS, EKS, Fargate
  • Storage: S3, EBS, EFS, FSx
  • Database: RDS, DynamoDB, Aurora, ElastiCache
  • Networking: VPC, Route53, CloudFront, ELB
  • Security: IAM, KMS, Secrets Manager, GuardDuty

Azure

  • Compute: VMs, Functions, AKS, Container Instances
  • Storage: Blob, Files, Disks, Data Lake
  • Database: SQL Database, Cosmos DB, Cache for Redis
  • Networking: VNet, Load Balancer, Application Gateway
  • Security: AAD, Key Vault, Security Center

Monitoring & Observability

Metrics

  • Prometheus: PromQL, exporters, alerting rules
  • Grafana: Dashboards, panels, variables, alerts
  • DataDog: APM, RUM, synthetics, logs
  • New Relic: Full-stack observability

Logging

  • ELK Stack: Elasticsearch, Logstash, Kibana
  • Loki: Log aggregation for Kubernetes
  • CloudWatch: AWS native logging
  • Splunk: Enterprise log analysis

Tracing

  • Jaeger: Distributed tracing
  • Zipkin: Trace collection and lookup
  • AWS X-Ray: AWS native tracing
  • OpenTelemetry: Vendor-neutral telemetry

Automation & Configuration

  • Ansible: Playbooks, roles, Ansible Tower
  • Puppet: Manifests, modules, Puppet Enterprise
  • Chef: Recipes, cookbooks, Chef Server
  • SaltStack: States, pillars, Salt Master

SRE Principles

  • SLIs/SLOs/SLAs: Define and measure service levels
  • Error Budgets: Balance reliability and feature velocity
  • Toil Reduction: Automate repetitive tasks
  • Postmortems: Blameless culture, action items
  • Chaos Engineering: Controlled failure injection
  • Capacity Planning: Load testing, resource forecasting
#devops#sre#kubernetes#terraform#ci-cd#monitoring

Source citations

Add this badge to your README

Show that Devops SRE Expert for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/agents/devops-sre-expert.svg)](https://heyclau.de/entry/agents/devops-sre-expert)

How it compares

Devops SRE Expert for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field
Kubernetes logoDevops SRE Expert for Claude

Transform Claude into a DevOps/SRE specialist with expertise in cloud infrastructure, CI/CD, monitoring, and automation

Open dossier
Kubernetes logoDevOps Engineer Agent - CI/CD, Terraform, Kubernetes

A Claude Code DevOps engineer persona grounded in GitHub Actions, Terraform, Docker, and Kubernetes. It writes and reviews CI/CD workflows, IaC, and deployment manifests using real tooling and documented commands.

Open dossier
Kubernetes Repository Contributor Agent for Claude

Source-backed Claude agent prompt for contributing to the official kubernetes/kubernetes repository using its AGENTS.md guidance for generated files, go.mod/go.work handling, staging source of truth, boilerplate, focused changes, tests, commit-message restrictions, make test, make verify, and make update workflows.

Open dossier
Production Reliability Engineer - Agents

Ensure production deployment reliability with SRE best practices. Monitors deployments, implements self-healing systems, and manages incident response for Claude Code apps.

Open dossier
Next steps
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffers——oktofeesh1—
Install riskReview firstReview firstReview firstReview first
Notes Safety · Privacy · Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandKubernetes logoKubernetesKubernetes logoKubernetes——
Categoryagentsagentsagentsagents
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorJSONboredJSONboredKubernetesJSONbored
Added2025-09-152025-10-162026-06-042025-10-25
Platforms
Claude Code
Claude Code
Claude Code
Claude Code
Source repo————
Safety notes— missing✓This persona produces commands and pipelines that modify real infrastructure: terraform apply, kubectl apply/rollout, docker build/run, and GitHub Actions deploy jobs. Review terraform plan output and use a saved plan file (-out) before apply. Deployment workflows can mutate production. Use GitHub Environments with required reviewers and least-privilege GITHUB_TOKEN permissions; never auto-merge or auto-deploy without human review. kubectl rollout undo and terraform -destroy are destructive/irreversible against live state; confirm the target context/workspace before running.✓This agent is for contributing to the official Kubernetes source repository, not for operating a live Kubernetes cluster or using a Kubernetes MCP server. Generated files such as `zz_generated.*` and `generated.pb.go` are read-only according to the reviewed AGENTS.md. Use `make update` instead of hand-editing generated output. The reviewed AGENTS.md says `go.mod` and `go.work` are generated. Do not run `go mod tidy`; use `hack/pin-dependency.sh` and `hack/update-vendor.sh` for dependency changes. The `staging/src/k8s.io/` tree is the source of truth for `k8s.io/*` packages. Do not import `k8s.io/kubernetes` from staging packages. Every `.go` file must keep the required Kubernetes boilerplate header. Repository commands can run package tests, integration tests, generators, formatters, verification suites, vendoring scripts, and update workflows that rewrite many files. Keep changes focused and reviewable, and add or update relevant tests instead of broad unrelated cleanup. Do not put `@mentions`, `fixes #...` keywords, or `Co-authored-by:` trailers in Kubernetes commit messages when the current AGENTS.md forbids them.✓Recommendations may include shell commands, package installs, or file edits; review and run any suggested changes yourself instead of applying them unverified.
Privacy notes— missing✓Terraform state files (.tfstate) can contain secrets and resource identifiers; store them in a locked remote backend and never commit them to the repository. Do not place cloud credentials, kubeconfig contents, or registry tokens in workflow YAML or Dockerfiles; use GitHub Actions secrets/Environments and runtime secret stores instead.✓Kubernetes repository work can expose package paths, API object names, test fixtures, generated diffs, integration-test logs, local cluster names, kubeconfig context names, environment variables, benchmark output, and failure traces. Do not paste private cluster names, kubeconfigs, service account tokens, cloud project IDs, proprietary manifests, undisclosed vulnerability details, customer logs, or local-only paths into prompts, public tests, issues, PRs, or generated output. Integration and E2E tests may create logs, temporary clusters, artifacts, or environment-specific output. Review and redact those artifacts before sharing them. Dependency and vendor changes can reveal internal forks, private module paths, or unreviewed replacement directives if copied from another environment. Keep dependency work inside the official Kubernetes workflow. When summarizing validation failures, redact local paths, hostnames, cluster names, credentials, private module names, and undisclosed security details.✓Guides Claude to read your repository files plus any code, logs, configuration, or credentials you share in the session; nothing is transmitted beyond the model, but review what you expose before sharing.
Prerequisites— none listed— none listed
  • A local checkout or source snapshot of the official `kubernetes/kubernetes` repository.
  • Review the current official `AGENTS.md` before using this agent, because generated-file, dependency, staging, boilerplate, command, and contributor rules can change.
  • Read the relevant Kubernetes contributor and developer guide sections before coding or proposing broad changes.
  • Go development environment and Kubernetes repository dependencies prepared when local validation is required.
— none listed
Install————
Config————
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Claude Process Automation

Automate business and engineering processes with headless Claude Code, GitHub Actions, and scheduled routines.

Review firstSource-backedReview firstAdded 8mo ago
Safety ✓ Privacy ✓by JSONbored
guides

Headless Claude Code Automation from Scripts and CI

Run Claude Code non-interactively with claude -p: bare mode, JSON output, piping, tool auto-approval, and CI authentication.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.