Open imyuanandyou opened 1 year ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
Continuously following, do not close
/cc @zheng1
/cc @zheng1
/assign @harrisonliu5
@zheng1 @harrisonliu5 请问有排期吗? 还在持续关注中 目前不得不把grpc健康检查关闭,但是影响生产环境应用
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
polish
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
polish
Describe the Bug https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/?spm=a2c4g.11186623.0.0.4841229cTTUstn#define-a-grpc-liveness-probe Kubernetes supports gRPC survival probe in version 1.24. When I define the gRPC survival probe, the pod console of kubesphere web will be blank and an error will be reported
Versions Used KubeSphere: v3.3.0 Kubernetes: 1.25
Expected behavior The web console can display correctly
The url I visited:org/clusters/default/projects/xxx-server/statefulsets/app-xxxx/resource-status