maaft
maaft
Hasura, please start working on this. It can't be that hard and would simplify our authorization flow **IMMENSLY** !
yes, I can access it (via `kubectl`) from the machine where I'm running `karmadactl register`. I'm not sure, why karmadactl even tries to resolve `karmada-apiserver.karmada-system.svc.cluster.local` on my local DNS, since...
I did some further debugging: `karmadaClusterInfo` in `pgk/karmadactl/register/register.go:340` contains this ```json { "LocationOfOrigin": "", "server": "https://karmada-apiserver.karmada-system.svc.cluster.local:5443", "certificate-authority-data": "LS0tLS1C..." } ``` Shouldn't there be `karmada-apiserver.example.com` instead?
Okay, I think I found the issue: 1. karmada retrieves control plane info using bootstrap token 2. this info contains `karmada-apiserver.karmada-system.svc.cluster.local` and not `karmada-apiserver.example.com` 3. agent kubeconfig is build with...
/subscribe This feature would be very awesome to have!
@RainbowMango is it already decided upon how to implement this? If yes and you can summarize what needs to be done, I can give it a shot. What speaks against...
@hholst80 how did you run your POC **without** the device-plugin (on GPU)?
same issue.
same issue here, also with DigitalOcean (didn't try other DNS services) ! It's a bit annoying.
Hi, any eta for this? I'd really like to use preemption and as far as I see, this is the only blocker left for v0.3! :rocket: