Open ashertz-dev opened 11 months ago
Thanks for letting us know @ashertz-dev. Unfortunately, there is no immediate fix for this, but we'll post any updates on this thread.
To anyone else facing this issue, please add a :+1: to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
Any update on that I have the exact same use case. Thanks.
@dannyneira
Hi, I just want to know you have roadmap to do this? It's really important for us who work as DevOps
Thanks!
Hi - I just want to confirm that this is a valid ask. I am working with multiple k8s clusters in parallel and the default ~/.kube/config is a limit I can overcome with mutliple terminal sessions each having its own kubeconfig set via $KUBECONFIG. I am happy to give WARP another try once this is available, but the missing context aware autocompletion is a deal breaker for me.
Discord username (optional)
ashertz
Describe the bug
Define kubeconfig files path by
KUBECONFIG
not workTo reproduce
~/.kube/ctx/config
~/.kube/config
fileExpected behavior
support using
KUBECONFIG
env auto completionScreenshots
Operating system
MacOS
Operating system and version
macOS 14.1.1
Shell Version
zsh 5.9 (x86_64-apple-darwin23.0)
Current Warp version
v0.2023.11.28.08.02.stable_00
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None