kubernetes-health-check

How to get a custom healthcheck path in a GCE L7 balancer serving a Kubernetes Ingress?

亡梦爱人 提交于 2019-12-05 13:11:53
问题 I'm trying to deploy a grafana instance inside Kubernetes (server 1.6.4) in GCE. I'm using the following manifests: Deployment (full version): apiVersion: apps/v1beta1 kind: Deployment metadata: name: grafana spec: replicas: 1 template: metadata: labels: name: grafana spec: initContainers: … containers: - name: grafana image: grafana/grafana readinessProbe: httpGet: path: /login port: 3000 … Service : apiVersion: v1 kind: Service metadata: name: grafana spec: selector: name: grafana ports: -

Should Health Checks call other App Health Checks

大城市里の小女人 提交于 2019-12-04 00:52:23
问题 I have two API's A and B that I control and both have readiness and liveness health checks. A has a dependency on B. A /foo - This endpoint makes a call to /bar in B /status/live /status/ready B /bar /status/live /status/ready Should the readiness health check for A make a call to the readiness health check for API B because of the dependency? 回答1: Service A is ready if it can serve business requests. So if being able to reach B is part of what it needs to do (which it seems it is) then it

Setting up a Kuberentes cluster with HTTP Load balancing ingress for RStudio and Shiny results in error pages

喜你入骨 提交于 2019-12-03 16:14:17
I'm attempting to create a cluster on Google Kubernetes Engine that runs nginx, RStudio server and two Shiny apps, following and adapting this guide . I have 4 workloads that are all green in the UI, deployed via: kubectl run nginx --image=nginx --port=80 kubectl run rstudio --image gcr.io/gcer-public/persistent-rstudio:latest --port 8787 kubectl run shiny1 --image gcr.io/gcer-public/shiny-googleauthrdemo:latest --port 3838 kubectl run shiny5 --image=flaviobarros/shiny-wordcloud --port=80 They were then all exposed as node ports via: kubectl expose deployment nginx --target-port=80 --type

RBAC Error in Kubernetes

痴心易碎 提交于 2019-12-02 12:35:15
问题 I have deployed kubernetes v1.8 in my workplace. I have created roles for admin and view access to namespaces 3months ago. In the initial phase RBAC is working as per the access given to the users. Now RBAC is not happening every who has access to the cluster is having clusteradmin access. Can you suggest the errors/changes that had to be done? 回答1: Ensure the RBAC authorization mode is still being used ( --authorization-mode=…,RBAC is part of the apiserver arguments) If it is, then check for

RBAC Error in Kubernetes

喜夏-厌秋 提交于 2019-12-02 04:27:17
I have deployed kubernetes v1.8 in my workplace. I have created roles for admin and view access to namespaces 3months ago. In the initial phase RBAC is working as per the access given to the users. Now RBAC is not happening every who has access to the cluster is having clusteradmin access. Can you suggest the errors/changes that had to be done? Ensure the RBAC authorization mode is still being used ( --authorization-mode=…,RBAC is part of the apiserver arguments) If it is, then check for a clusterrolebinding that is granting the cluster-admin role to all authenticated users: kubectl get

Kubernetes liveness probes with query string parameters

a 夏天 提交于 2019-12-01 06:33:19
I've looked over the documentation and browsed the source, but I can't seem to figure out how to do this. Is there any way to send query string parameters along with the path when implementing a Kubernetes liveness probe? The string I am sending, which looks something like this: /api/v1?q=... becomes URL-encoded and hits the server as: /api/v1%3fq=... As I have no such route on this particular API, I get a 404, and Kube reaps the pods after the allotted timeout. Is there any way to define query string parameters to liveness probes and/or trick the URI encoder to allow query string parameters?

What is the default value of initialDelaySeconds

喜夏-厌秋 提交于 2019-11-30 18:41:38
Kubernetes' liveness and readiness prob for pods (deployment) can be configured with this initial delay ---- meaning the prob will start after this many sends after the container is up. If it is not specified, what is the default value? I can't seem to find it. The default value for periodSeconds is documented as 10 second. Thanks It seems that the default value of 0 is missing from the documentation . The health or readiness check algorithm works like this: Wait for initialDelaySeconds Perform readiness check and wait timeoutSeconds for a timeout If the number of continued successes is

What is the default value of initialDelaySeconds

醉酒当歌 提交于 2019-11-30 16:45:41
问题 Kubernetes' liveness and readiness prob for pods (deployment) can be configured with this initial delay ---- meaning the prob will start after this many sends after the container is up. If it is not specified, what is the default value? I can't seem to find it. The default value for periodSeconds is documented as 10 second. Thanks 回答1: It seems that the default value of 0 is missing from the documentation. The health or readiness check algorithm works like this: Wait for initialDelaySeconds