https://kubeclipper.io/v1.7/en/docs/faq/Recent content in FAQ on KubeclipperHugo -- gohugo.ioFri, 02 Dec 2022 00:00:00 +0000https://kubeclipper.io/v1.7/en/docs/faq/kcctl-create-cluster-error/Mon, 01 Jan 0001 00:00:00 +0000https://kubeclipper.io/v1.7/en/docs/faq/kcctl-create-cluster-error/ <p>This page applies to 1.7. Older v1.2.1 Calico download workarounds do not apply directly to this release.</p> <h2 id="cluster-not-ready-after-submission">Cluster not Ready after submission</h2> <div class="highlight"><pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-bash" data-lang="bash"><span style="display:flex;"><span>kcctl operation list -c demo </span></span><span style="display:flex;"><span>kcctl get cluster demo -o yaml </span></span><span style="display:flex;"><span>kcctl get node </span></span></code></pre></div><p>Inspect operation details and logs next. Request acceptance, operation completion, and Kubernetes node readiness are separate checks.</p> <h2 id="offline-package-or-image-errors">Offline package or image errors</h2> <p>Use <code>kcctl resource list</code> to confirm version and architecture. Inspect image paths, authentication, and connectivity using the failed step&rsquo;s logs. See <a href="https://kubeclipper.io/v1.7/en/docs/getting-started/carete-k8s-cluster-offline/">offline clusters</a>.</p> <h2 id="platform-or-agent-errors">Platform or Agent errors</h2> <p>Run <code>kcctl status</code> and <code>kcctl doctor</code> to check API access, services, and SSH connectivity. Supply an SSH private key as deployment credentials, not a public key path.</p> <p>See <a href="https://kubeclipper.io/v1.7/en/docs/tutorials/diagnostics/">platform diagnostics</a> for the investigation sequence and <a href="https://kubeclipper.io/v1.7/en/docs/tutorials/operations/">operations and logs</a> for retries and cancellation.</p>