Open datho7561 opened 5 months ago
It seems like it's checking the status of the cluster, but I don't see why this would be needed for this command.
odo preference view
lists all the Devfile Registries odo
can use, and (since odo v3.8.0
) it also tries to list those coming from the current cluster. That's why it is trying to contact the current cluster.
More details in https://odo.dev/docs/user-guides/advanced/using-in-cluster-devfile-registry/
Actual behavior
Takes around 40 seconds
I guess any oc
/kubectl
command communicating with the cluster would take the same amount of time, right?
Okay, thanks! I didn't know that the cluster could provide Devfiles
I guess any oc/kubectl command communicating with the cluster would take the same amount of time, right?
Yes, odo version
takes around the same amount of time as odo preference view
.
A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.
/remove-lifecycle stale /lifecycle frozen
/kind bug
What versions of software are you using?
Operating System: Fedora 39
Output of
odo version
:How did you run odo exactly?
Set my
~/.kube/config
to point to mycrc
cluster, which is stopped. Then I run :odo preference view -o json
Actual behavior
Takes around 40 seconds
Expected behavior
Takes < 1 second
Any logs, error output, etc?