This message was deleted.
# k3d
a
This message was deleted.
b
I imagine you're getting that output during the
wait
command, right?
kubectl
will still reference the metrics api if it's listed in
apiservices
, which is independent of whether the service is actually available - you have a kind of chicken/egg problem. Is the error output causing some issue?
kubectl get apiservices <http://v1beta1.metrics.k8s.io|v1beta1.metrics.k8s.io>
will show whether it's available or not. You may be able to
wait
on that
h
Running time kubectl -n kube-system wait apiservices v1beta1.metrics.k8s.io --for=condition=Available --timeout=5m Did fix this issue
👍 1