kubesphere / kubesphere

The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
https://kubesphere.io
Other
15k stars 2.14k forks source link

Kubesphere does not support grpc probe health check #5439

Open imyuanandyou opened 1 year ago

imyuanandyou commented 1 year ago

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

       livenessProbe:
         failureThreshold: 3
         grpc:
           port: 7001
           service: ""
         initialDelaySeconds: 20
         periodSeconds: 15
         successThreshold: 1
         timeoutSeconds: 2
       readinessProbe:
         failureThreshold: 3
         grpc:
           port: 7001
           service: ""
         initialDelaySeconds: 10
         periodSeconds: 3
         successThreshold: 1
         timeoutSeconds: 2

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

kubesphere
stale[bot] commented 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.

blocksec-aws commented 1 year ago

Continuously following, do not close

VioZhang commented 1 year ago

/cc @zheng1

imyuanandyou commented 1 year ago

/cc @zheng1

zheng1 commented 1 year ago

/assign @harrisonliu5

imyuanandyou commented 1 year ago

@zheng1 @harrisonliu5 请问有排期吗? 还在持续关注中 目前不得不把grpc健康检查关闭,但是影响生产环境应用

stale[bot] commented 9 months 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.

imyuanandyou commented 9 months ago

polish

stale[bot] commented 6 months 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.

imyuanandyou commented 5 months ago

polish