Ken Rider
Ken Rider
When I changed the cluster provider to generic I was able to delete the HelmRelease I wasn't able to delete before.
I'm guessing that it assumed it was an AKS cluster because the API endpoint was `...westus2.cloudapp.azure.com:6443`.
The logic in the code isn't sufficient to determine if it's AKS or not. The provider ID for my nodes matches. ``` providerID: azure:///subscriptions/a0b0c0d0-e1f1-a2b2-c3d3-abcdef123456/resourceGroups/kdr-tkg/providers/Microsoft.Compute/virtualMachines/tkg-workload-azure-md-0-2qm74 ``` The only thing I can...
On your other question, at least so far it has kept its Generic designation.
@kingdonb, in looking at the nodes in an AKS cluster, you might be better off checking the series of `kubernetes.azure.com/*` labels that are applied to the AKS nodes. I checked...
I tried kubeman on another laptop with only one cluster and user configured. I get the same error. I don't see any log files specific to kubeman and I don't...
Of course, now that I see the (obvious) way to debug, I can't seem to duplicate the problem. I do have another problem but it's unrelated so I'll open a...
Reopening as I ran into this problem again and have the debug console output for it. The cluster/context had been working just a few minutes ago but now I'm getting...
BTW, `kubectl` commands with this context are working fine.
`ucp_test-ucp.lab.capstonec.net` is part of the context name and not resolvable. The server name in the cluster spec is https://test-ucp.lab.capstonec.net:6443. I can resolve test-ucp.lab.capstonec.net (it's a CNAME for a load balancer...