Merge pull request #72 from ngopalak-redhat/ngopalak/cluster_options

Add claude interactive cluster creation, readme and destroy command

Author: openshift-merge-bot[bot]

plugins/openshift/README.md

@@ -16,10 +16,22 @@ This command automates the complex process of rebasing OpenShift forks following
 
 ### `/openshift:bump-deps`
 
-Automates the process of bumping dependencies in OpenShift organization projects. It analyzes the dependency, determines 
-the appropriate version to bump to, updates the necessary files (go.mod, go.sum, package.json, etc.), runs tests, 
+Automates the process of bumping dependencies in OpenShift organization projects. It analyzes the dependency, determines
+the appropriate version to bump to, updates the necessary files (go.mod, go.sum, package.json, etc.), runs tests,
 and optionally creates Jira tickets and pull requests.
 
+### `/openshift:create-cluster`
+
+Extract OpenShift installer from release image and create an OCP cluster.
+
+This command automates the process of extracting the installer from a release image and creating a new OpenShift cluster on various platforms (AWS, Azure, GCP, vSphere, OpenStack).
+
+### `/openshift:destroy-cluster`
+
+Destroy an OpenShift cluster created by the create-cluster command.
+
+This command safely destroys a cluster and cleans up all cloud resources. Includes safety confirmations and optional backup of cluster information.
+
 See the [commands/](commands/) directory for full documentation of each command.
 
 ## Installation
@@ -122,6 +134,119 @@ Automates dependency updates in OpenShift projects with comprehensive analysis,
 
 See [commands/bump-deps.md](commands/bump-deps.md) for full documentation.
 
+### Cluster Management
+
+#### `/openshift:create-cluster` - Create OCP Clusters
+
+Extract the OpenShift installer from a release image and create a new OpenShift Container Platform cluster. This command automates installer extraction and cluster creation for development and testing purposes.
+
+**⚠️ Important**: This is a last-resort tool. For most workflows, use **Cluster Bot**, **Gangway**, or **Multi-PR Testing in CI** instead. Only use this when you need full control over cluster configuration or are testing installer changes.
+
+**Basic Usage:**
+```bash
+# Interactive mode (prompts for all options)
+/openshift:create-cluster
+
+# With release image and platform
+/openshift:create-cluster quay.io/openshift-release-dev/ocp-release:4.21.0-ec.2-x86_64 aws
+
+# With CI build
+/openshift:create-cluster registry.ci.openshift.org/ocp/release:4.21.0-0.ci-2025-10-27-031915 gcp
+```
+
+**Prerequisites:**
+- OpenShift CLI (`oc`) installed
+- Cloud provider credentials configured (AWS, Azure, GCP, etc.)
+- Pull secret from [Red Hat Console](https://console.redhat.com/openshift/install/pull-secret)
+- Domain/DNS configuration (e.g., Route53 hosted zone for AWS)
+
+**Supported Platforms:**
+- AWS (Amazon Web Services)
+- Azure (Microsoft Azure)
+- GCP (Google Cloud Platform)
+- vSphere (VMware vSphere)
+- OpenStack
+- none (Bare metal / platform-agnostic)
+
+**Key Features:**
+- Automatic installer extraction from release images
+- Version-specific installer caching
+- Interactive configuration generation
+- Post-installation verification
+- Cluster credentials and access information
+
+**Arguments:**
+- `[release-image]` (optional): OpenShift release image (prompted if not provided)
+- `[platform]` (optional): Target platform (prompted if not provided)
+
+**Examples:**
+
+1. Create cluster with production release on AWS:
+   ```bash
+   /openshift:create-cluster quay.io/openshift-release-dev/ocp-release:4.21.0-ec.2-x86_64 aws
+   ```
+
+2. Create cluster with CI build interactively:
+   ```bash
+   /openshift:create-cluster registry.ci.openshift.org/ocp/release:4.21.0-0.ci-2025-10-27-031915
+   ```
+
+3. Full interactive mode:
+   ```bash
+   /openshift:create-cluster
+   ```
+
+See [commands/create-cluster.md](commands/create-cluster.md) for full documentation.
+
+#### `/openshift:destroy-cluster` - Destroy OCP Clusters
+
+Safely destroy an OpenShift Container Platform cluster that was created using `/openshift:create-cluster`. This command handles cleanup of all cloud resources with built-in safety confirmations.
+
+**⚠️ WARNING**: This operation is **irreversible** and permanently deletes all cluster resources and data.
+
+**Basic Usage:**
+```bash
+# Interactive mode (searches for installation directories)
+/openshift:destroy-cluster
+
+# With specific installation directory
+/openshift:destroy-cluster ./my-cluster-install-20251028-120000
+
+# With full path
+/openshift:destroy-cluster /path/to/cluster-install-dir
+```
+
+**Safety Features:**
+- Requires explicit "yes" confirmation before destruction
+- Displays cluster information before proceeding
+- Optional backup of cluster credentials and metadata
+- Validates installation directory and metadata
+- Provides manual cleanup instructions if automated cleanup fails
+
+**What Gets Deleted:**
+- All cluster VMs and compute resources
+- Load balancers and networking resources
+- Storage volumes and persistent data
+- DNS records (if managed by installer)
+- All cluster configuration
+
+**Arguments:**
+- `[install-dir]` (optional): Path to cluster installation directory (prompted if not provided)
+
+**Examples:**
+
+1. Destroy cluster interactively:
+   ```bash
+   /openshift:destroy-cluster
+   ```
+
+2. Destroy specific cluster:
+   ```bash
+   /openshift:destroy-cluster ./test-cluster-install-20251028-120000
+   ```
+
+See [commands/destroy-cluster.md](commands/destroy-cluster.md) for full documentation.
+
 ## Development
 
 ### Adding New Commands

plugins/openshift/commands/create-cluster.md

@@ -1,6 +1,6 @@
 ---
 description: Extract OpenShift installer from release image and create an OCP cluster
-argument-hint: [release-image] [platform] [options]
+argument-hint: "[release-image] [platform] [options]"
 ---
 
 ## Name
@@ -106,8 +106,8 @@ If arguments are not provided, the command will interactively prompt for:
 - **base-domain** (required): Base domain for the cluster
   - Example: `example.com` → Cluster API will be `api.{cluster-name}.{base-domain}`
 
-- **pull-secret** (optional): Path to pull secret file
-  - Default: `~/pull-secret.txt`
+- **pull-secret** (required): Path to pull secret file
+  - User will be prompted to provide the path
 
 - **installer-dir** (optional): Directory to store/find installer binaries
   - Default: `~/.openshift-installers`
@@ -219,22 +219,118 @@ mkdir -p "$INSTALL_DIR"
 cd "$INSTALL_DIR"
 ```
 
-### 5. Generate install-config.yaml
+### 5. Collect Required Information and Generate install-config.yaml
+
+**IMPORTANT**: Do NOT run the installer interactively. Instead, collect all required information from the user and generate the install-config.yaml programmatically.
+
+**Step 5.1: Collect Information**
+
+Prompt the user for the following information (if not already provided as arguments):
+
+1. **SSH Public Key**:
+   - Check for existing SSH keys: `ls -la ~/.ssh/*.pub`
+   - Ask user to select from available keys or specify path
+   - Default: `~/.ssh/id_rsa.pub`
+
+2. **Platform** (if not provided as argument):
+   - Ask user to select: aws, azure, gcp, vsphere, openstack, none
+
+3. **Platform-specific details**:
+   - For AWS:
+     - Region (e.g., us-east-1, us-west-2)
+   - For Azure:
+     - Region (e.g., centralus, eastus)
+     - Cloud name (e.g., AzurePublicCloud)
+   - For GCP:
+     - Project ID
+     - Region (e.g., us-central1)
+   - For other platforms: collect required platform-specific info
+
+4. **Base Domain**:
+   - Ask for base domain (e.g., example.com, devcluster.openshift.com)
+   - Validate that domain is configured (e.g., Route53 hosted zone for AWS)
+
+5. **Cluster Name**:
+   - Ask for cluster name or use default: `ocp-cluster`
+   - Validate DNS compatibility (lowercase, hyphens only)
+
+6. **Pull Secret**:
+   - **IMPORTANT**: Always ask user to provide the path to their pull secret file
+   - Do NOT use default paths like `~/pull-secret.txt` or `~/Downloads/pull-secret.txt`
+   - Prompt: "Please provide the path to your pull secret file (download from https://console.redhat.com/openshift/install/pull-secret):"
+   - Read contents of pull secret file from the provided path
+
+**Step 5.2: Generate install-config.yaml**
+
+Create the install-config.yaml file programmatically based on collected information:
 
-Run the installer's interactive config generation:
 ```bash
-"$INSTALLER_PATH" create install-config --dir=.
+# Read SSH public key
+SSH_KEY=$(cat "$SSH_KEY_PATH")
+
+# Read pull secret
+PULL_SECRET=$(cat "$PULL_SECRET_PATH")
+
+# Generate install-config.yaml
+cat > install-config.yaml <<EOF
+apiVersion: v1
+baseDomain: ${BASE_DOMAIN}
+metadata:
+  name: ${CLUSTER_NAME}
+compute:
+- name: worker
+  replicas: 3
+controlPlane:
+  name: master
+  replicas: 3
+networking:
+  networkType: OVNKubernetes
+  clusterNetwork:
+  - cidr: 10.128.0.0/14
+    hostPrefix: 23
+  serviceNetwork:
+  - 172.30.0.0/16
+platform:
+  ${PLATFORM}:
+    region: ${REGION}
+pullSecret: '${PULL_SECRET}'
+sshKey: '${SSH_KEY}'
+EOF
 ```
 
-This will interactively prompt for:
-- SSH public key
-- Platform selection
-- Platform-specific details (region, instance types, etc.)
-- Base domain
-- Cluster name
-- Pull secret
+**Platform-specific configurations**:
+
+For **AWS**:
+```yaml
+platform:
+  aws:
+    region: us-east-1
+```
+
+For **Azure**:
+```yaml
+platform:
+  azure:
+    region: centralus
+    baseDomainResourceGroupName: ${RESOURCE_GROUP_NAME}
+    cloudName: AzurePublicCloud
+```
+
+For **GCP**:
+```yaml
+platform:
+  gcp:
+    projectID: ${PROJECT_ID}
+    region: us-central1
+```
+
+For **None/Baremetal**:
+```yaml
+platform:
+  none: {}
+```
 
-**IMPORTANT**: Always backup install-config.yaml before proceeding:
+**IMPORTANT**: Always backup install-config.yaml after creation:
 ```bash
 cp install-config.yaml install-config.yaml.backup
 ```
@@ -336,7 +432,8 @@ cd $INSTALL_DIR
 
 1. **Pull secret not found**:
    - Download from https://console.redhat.com/openshift/install/pull-secret
-   - Save to `~/pull-secret.txt`
+   - Save to a secure location of your choice
+   - Provide the path when prompted during cluster creation
 
 2. **Insufficient cloud quotas**:
    - Check cloud provider quota limits