openshift

OpenShift enterprise Kubernetes platform. Use for enterprise K8s.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

openshift is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

OpenShift enterprise Kubernetes platform. Use for enterprise K8s.

Teams using openshift should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/openshift/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/devops/openshift/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/openshift/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How openshift Compares

Feature / Agent	openshift	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

OpenShift enterprise Kubernetes platform. Use for enterprise K8s.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# OpenShift

Red Hat OpenShift is an enterprise-ready Kubernetes container platform with full-stack automated operations. In 2025, **OpenShift Virtualization** (running VMs side-by-side with containers) is a key feature.

## When to Use

- **Hybrid Cloud**: Consistent experience across On-Prem and Cloud.
- **Enterprise Requirements**: Built-in strict security (SCC), registry, monitoring, and CI/CD.
- **VM Migration**: Lift-and-shift VMs into K8s using OpenShift Virtualization (KubeVirt).

## Quick Start (OC CLI)

```bash
# Login
oc login -u developer -p developer https://api.crc.testing:6443

# Create Project (Namespace)
oc new-project my-app

# Deploy from Source (Source-to-Image)
oc new-app nodejs~https://github.com/sclorg/nodejs-ex.git
```

## Core Concepts

### Source-to-Image (S2I)

Build container images directly from source code without writing a Dockerfile. OpenShift detects the language (Node/Java/Python) and builds it.

### Routes

OpenShift's native ingress controller. Used long before K8s Ingress/Gateway API.

### Operators

First-class citizens. Everything in OpenShift is managed by an Operator.

## Best Practices (2025)

**Do**:

- **Use OpenShift GitOps**: ArgoCD is fully integrated.
- **Use `oc`**: It is a superset of `kubectl`. You rarely need `kubectl` on OpenShift.
- **Leverage Virtualization**: Run legacy Windows/Linux VMs as Pods to decommission old VMWare clusters.

**Don't**:

- **Don't run as root**: OpenShift forbids this by default. Don't disable SCCs (Security Context Constraints) just to make a bad image work. Fix the image.

## References

- [OpenShift Documentation](https://docs.openshift.com/)