Skip to content

fix(e2e): backport Get kubeconfig step to plugin-e2e workflow#167

Open
privilegedescalation-engineer[bot] wants to merge 1 commit intomainfrom
hugh/fix-e2e-kubeconfig-step
Open

fix(e2e): backport Get kubeconfig step to plugin-e2e workflow#167
privilegedescalation-engineer[bot] wants to merge 1 commit intomainfrom
hugh/fix-e2e-kubeconfig-step

Conversation

@privilegedescalation-engineer
Copy link
Copy Markdown
Contributor

Summary

Backports the robust Get kubeconfig step from the main-worktree copy of plugin-e2e.yaml into the .github reusable workflow.

Problem

The reusable plugin-e2e.yaml workflow (invoked by all Headlamp plugin repos) was missing the Get kubeconfig step. This step handles multiple kubeconfig fallback paths instead of assuming a pre-configured kubeconfig at a fixed path. E2E runs on runners-privilegedescalation (self-hosted ARC runners) were failing with startup_failure because the runner pod had no valid kubeconfig before attempting to deploy the E2E Headlamp instance.

Fix

Added lines 40–75 (Get kubeconfig step) from the main-worktree version into .github/workflows/plugin-e2e.yaml, inserting it between Setup kubectl and Install dependencies steps.

Testing

  • CI lint and build steps pass
  • E2E runs will be monitored for startup_failure recurrence; fix is considered verified if no further startup_failure on runners-privilegedescalation over 5 consecutive runs

The reusable plugin-e2e.yaml workflow was missing the robust Get kubeconfig
step that the main-worktree copy has. This step handles multiple kubeconfig
fallback paths (runner config, home kubeconfig, in-cluster service account)
instead of assuming a pre-configured kubeconfig at a fixed path.

This fixes startup failures in E2E runs where the runner pod could not
locate a valid kubeconfig before deploying the E2E Headlamp instance.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant