https://krkn-chaos.dev/tags/troubleshooting/Recent content in Troubleshooting on KrknHugoenhttps://krkn-chaos.dev/docs/developers-guide/custom-scenario/troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://krkn-chaos.dev/docs/developers-guide/custom-scenario/troubleshooting/<p>First determine whether the scenario was discovered, whether its image was pulled, and whether its process started. These are separate checkpoints. Kubernetes events explain scheduling and pull failures; container logs explain startup and plugin failures.</p> <h2 id="the-scenario-is-visible-but-the-pull-attempts-https"> The scenario is visible, but the pull attempts HTTPS <a class="td-heading-self-link" href="#the-scenario-is-visible-but-the-pull-attempts-https" aria-label="Heading self-link"></a> </h2> <p>Typical event:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">http: server gave HTTP response to HTTPS client </span></span></code></pre></div><p>The operator&rsquo;s registry client successfully used HTTP to list metadata. Kubelet then asked containerd to pull the image, and containerd defaulted to HTTPS. Krknctl&rsquo;s <code>insecure</code> setting does not configure the node runtime.</p>