Hcp Create Agent

Before creating the cluster, verify your agents are available:

Check agents in namespace:
  kubectl get agents -n <agent-namespace>

Verify agent status:
  kubectl describe agents -n <agent-namespace>

Ensure agents are:
  - In "Available" state
  - Not bound to other clusters
  - Meet minimum resource requirements

hypershift create cluster agent \
  --name <cluster-name> \
  --namespace <cluster-name>-ns \
  --agent-namespace <agent-namespace> \
  --pull-secret <pull-secret-path> \
  --release-image <release-image> \
  --base-domain <base-domain>

hypershift create cluster agent \
  --name edge-cluster \
  --namespace edge-cluster-ns \
  --agent-namespace default \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain edge.local \
  --control-plane-availability-policy SingleReplica \
  --node-pool-replicas 1

hypershift create cluster agent \
  --name production-cluster \
  --namespace production-cluster-ns \
  --agent-namespace agent-system \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain example.com \
  --control-plane-availability-policy HighlyAvailable \
  --node-pool-replicas 3 \
  --auto-repair

hypershift create cluster agent \
  --name secure-cluster \
  --namespace secure-cluster-ns \
  --agent-namespace agent-system \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain internal.example.com \
  --image-content-sources /path/to/image-content-sources.yaml \
  --additional-trust-bundle /path/to/ca-bundle.pem \
  --render

hypershift create cluster agent \
  --name compliance-cluster \
  --namespace compliance-cluster-ns \
  --agent-namespace agent-system \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain secure.example.com \
  --fips

## Post-Creation Configuration (Disconnected)

After running the command above (with --render), you'll need to modify the generated manifests:

1. **Add ImageContentSources to HostedCluster:**
```yaml
spec:
  imageContentSources:
  - source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
    mirrors:
    - registry.example.com:5000/openshift/release
  - source: quay.io/openshift-release-dev/ocp-release
    mirrors:
    - registry.example.com:5000/openshift/release-images
  - source: registry.redhat.io/multicluster-engine
    mirrors:
    - registry.example.com:5000/openshift/multicluster-engine
```

2. **Disable Default OperatorHub Sources:**
```yaml
spec:
  configuration:
    operatorhub:
      disableAllDefaultSources: true
```

3. **Apply the manifests:**
```bash
kubectl apply -f <rendered-manifest-files>
```

## Next Steps

1. **Verify agents are available:**
   kubectl get agents -n <agent-namespace>

2. **Monitor cluster creation:**
   kubectl get hostedcluster -n <cluster-namespace>
   kubectl get nodepool -n <cluster-namespace>

3. **Check agent assignment:**
   kubectl get agents -n <agent-namespace> -o wide

4. **Access cluster when ready:**
   hypershift create kubeconfig --name <cluster-name> --namespace <cluster-namespace>

No agents found in namespace "default".

Please ensure:
1. Agents are registered and visible via `kubectl get agents -A`
2. Agents are in "Available" state
3. Correct namespace specified

Check agents:
  kubectl get agents -A

Register new agents using the agent-based installer or manual process.

Only 2 agents available, but you requested 3 node replicas.

Options:
1. Reduce node-pool-replicas to 2
2. Register additional agents
3. Use SingleReplica control plane (reduces total requirement)

Would you like me to adjust the configuration?

Some agents are already bound to other clusters.

Available agents: 1
Bound agents: 2

Check agent status:
  kubectl describe agents -n <namespace>

Free up agents by deleting unused clusters or register new agents.

Release image access failed. In disconnected environments:

1. Ensure mirror registry contains required images
2. Verify image-content-sources file mapping
3. Check custom CA bundle configuration
4. Validate network connectivity to mirror registry

Mirror required images using:
  oc adm release mirror --to <mirror-registry>

"Create cluster with autoscaling"

Not checking agent availability before cluster creation

Using public image references in airgapped environment

Using minimal agents for production workloads

Input: "small edge cluster for remote office monitoring"

Analysis:
- Environment: Edge
- Scale: Minimal
- Use case: Monitoring

Generated Command:
hypershift create cluster agent \
  --name edge-monitoring \
  --namespace edge-monitoring-ns \
  --agent-namespace default \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain edge.local \
  --control-plane-availability-policy SingleReplica \
  --node-pool-replicas 1

Input: "airgapped production cluster for financial data processing"

Analysis:
- Environment: Disconnected/Secure
- Scale: Production
- Use case: Financial (compliance required)

Generated Command:
hypershift create cluster agent \
  --name financial-prod \
  --namespace financial-prod-ns \
  --agent-namespace secure-agents \
  --pull-secret /path/to/pull-secret.json \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi \
  --base-domain secure.financial.internal \
  --image-content-sources /path/to/image-content-sources.yaml \
  --additional-trust-bundle /path/to/ca-bundle.pem \
  --fips \
  --render