Open maneeshmp opened 1 year ago
I have the same error, but I am using cluster on OCI. I am able to connect with the cluster when using kubectl
.
I wonder if headlamp is unable to handle authentication with command, like oci
?
This is what in my kubeconfig at the moment:
users:
- name: user-foo
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
command: oci
args:
- ce
- cluster
- generate-token
- --cluster-id
- foo
- --region
- bar
env: []
Having the same problem on this end. Noting the following
kubectl
commands work without issueHey folks, as some of you have mentioned Headlamp doesn't support authentication via commands like kubelogin or oci yet. This is a known issue and is on our list.
@yolossn @joaquimrocha This was removed 0.22.0, is it planned?
Hey @shlomiassaf, It is planned, we will work on it in an upcoming release. Recently I discovered that the CLI based authentication is supported partially. Incase you are facing this with AKS run kubelogin convert-kubeconfig -l azurecli
and check if it works for you.
Hey folks. ( @aravol @shlomiassaf @winston0410 @maneeshmp )
The latest release includes a few fixes for this. I wonder if it works for you?
We have an Azure AD integrated AKS cluster. I have only namespace level access. When I start headlamp, i get a bad gateway error. Under settings I have configured the namespaces I have access still the same error was displayed. I am using the latest version of headlamp downloaded from site.