exec fails to enter the container

Open
#234 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
gcp, kubernetes, rust

Research direction

Start by reproducing the pod selection and exec flow with the reported kubectl and server versions, then trace the CLI's kubectl invocation and GCP credential handling. Done means exec successfully enters the selected container without the removed gcp auth plugin error.

Written by the indexing model from the issue text.

Description

After a pod selected in click, previous and new version 0.6.3 with the GCP auth changes the exec to run commands inside the container is lost, only error messages are raised.
error: The gcp auth plugin has been removed. Please use the "gke-gcloud-auth-plugin" kubectl/client-go credential plugin instead. See https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke for further details Error running command: kubectl exited abnormally
Info versions:
kubectl version
Client Version: v1.33.5-dispatcher
Kustomize Version: v5.6.0
Server Version: v1.33.5-gke.2118001

Dominant language
Rust
Stars
1.5k
Forks
93
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/click

All issues in databricks/click

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.