PR Workflow

Automate cloning, branching, fixing, validating, and opening pull requests for kubernetes-manifests.

9|3|Updated Apr 16, 2024
One-click install
npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill pr-workflow-keiretsu-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PR Workflow
Source: https://github.com/keiretsu-labs/kubernetes-manifests/tree/main/openclaw/workspaces/main/skills/pr-workflow
Command: npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill pr-workflow-keiretsu-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the entire process of fixing issues within the kubernetes-manifests repository, from cloning and branching to validation and opening a pull request.

Core Features & Use Cases

  • Automated Git Workflow: Handles cloning, branching, committing, and pushing changes to the kubernetes-manifests repository.
  • Integrated Validation: Includes steps to validate YAML syntax and Kustomize builds before committing.
  • PR Creation: Generates a well-formatted pull request with a conventional commit message and a descriptive body.
  • Use Case: When a CoreDNS pod in the talos-ottawa cluster is OOMKilled due to insufficient memory, this Skill can be used to increase its resource limits, validate the change, commit it, and open a PR for review.

Quick Start

Use the PR Workflow skill to fix the coredns memory limit on the Ottawa cluster.

Frequently Asked Questions about PR Workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Kubernetes manifest pull requests for resource limit changes?

Automating Kubernetes manifest pull requests involves cloning, branching, modifying YAML configurations, validating syntax, and opening a PR. This workflow handles resource limits, HelmRelease values, and Flux kustomization configurations automatically using Git, gh CLI, yq, and kustomize.

What tools do I need to validate Kustomize builds before opening a Flux kustomization PR?

Validating Kustomize builds before opening a Flux kustomization PR requires Git, gh CLI, yq, and kustomize installed in your environment. These tools enable YAML syntax validation and build verification to ensure manifest changes are correctly formatted before submission.

Can I fix OOMKilled pods by updating Kubernetes resource limits through an automated Git workflow?

Fixing OOMKilled pods by updating Kubernetes resource limits through an automated Git workflow is fully supported. The process modifies resource limits in the kubernetes-manifests repository, validates the YAML syntax, commits the change, and generates a well-formatted pull request for review.

How does automated PR creation work for Kubernetes namespace labels and HelmRelease values?

Automated PR creation for Kubernetes namespace labels and HelmRelease values works by cloning the kubernetes-manifests repository, applying the necessary YAML modifications, validating Kustomize builds, and pushing a branch with a conventional commit message to generate a descriptive pull request.

What is the best way to manage Flux kustomization configuration changes across Kubernetes clusters?

Managing Flux kustomization configuration changes across Kubernetes clusters is best handled by automating the clone, branch, fix, validate, and PR cycle. This ensures all modifications to the kubernetes-manifests repository are validated and reviewed before being merged into the cluster configuration.