-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the server could not find the requested resource #501
Comments
cluster日志: root@crms-10-10-178-147[/k8s/fate]# kubefate cluster logs 4f14f1ca-687c-49cf-a1b7-f9a48e7b37bd |
我也遇到同样的问题,不过我的日志中主要错误是 fateboard 访问 fateflow 9380 服务出错:
测试发现其他 pod 内(比如 clustermanager)可以正常访问 fateflow 9380 服务,就 fateboard 不行。 |
也遇到这个错误 [root demo]# kubefate cluster describe b93ac837-aaca-4040-9066-c33d6ca7f5f8 |
我也遇到这个问题,这个问题到现在还没解决吗?以下是我的log [mysql-c88469467-j57b7 mysql] 2022-03-02 07:05:01+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.28-1debian10 started. |
Check the version of cli and service through |
确认过版本一致,问题一直存在 |
This bug will appear in k8s v1.22+ |
A temporary solution is to use k8s <=v1.21 |
Convert to task: to support k8s > v1.2.1 |
2022年3月22日,使用minikube搭建集群,该问题依旧存在 |
root@crms-10-10-178-147[/k8s/fate]# kubefate cluster ls
UUID NAME NAMESPACE REVISION STATUS CHART ChartVERSION AGE
4f14f1ca-687c-49cf-a1b7-f9a48e7b37bd fate-9999 fate-9999 1 Running fate v1.7.0 19m
root@crms-10-10-178-147[/k8s/fate]# kubefate cluster describe 4f14f1ca-687c-49cf-a1b7-f9a48e7b37bd
the server could not find the requested resource
root@crms-10-10-178-147[/k8s/fate]# the server could not find the requested resource
为什么没有描述信息
The text was updated successfully, but these errors were encountered: