continuouspipe / kube-status

Status of a Kubernetes cluster via an API

ContinuousPipe is the open-source continuous deployment pipeline for containerized applications. It listens to your code repository changes, builds your Docker images and deploy them to your Kubernetes cluster(s).

Usage

• Install ContinuousPipe on your machine or Kubernetes cluster to get started.
• Check out the website or read the documentation to know more.

Contributing

ContinuousPipe is Open Source. You are warmly welcome to contribute, we want you! You can install ContinuousPipe on your development environment with DockerCompose and start working on the source code but keep in mind that helping with the documentation and/or supporting others is as much valuable 💖

Community

• Join our Slack community
• Follow our Twitter
• Feel free to open issues and pull-requests to this repository!

kube-status's Issues

Supports GKE RBAC credentials

When using GKE and RBAC, you need to use Google Service Account to connect to the Kubernetes cluster. We need to support this type of credentials.

Add hosts events and conditions

In order to identify potential issues with the hosts, we need to store their events and conditions

Identify raisons of non-running pods such as the "FailedSync"

One of the main issues we have with volumes is the "FailedSync" and the mount timeouts.

Events:
  FirstSeen	LastSeen	Count	From								SubobjectPath	Type		Reason		Message
  ---------	--------	-----	----								-------------	--------	------		-------
  4m		4m		1	{default-scheduler }								Normal		Scheduled	Successfully assigned postgres-1015904327-0cq7c to [...]-pool-4cpu-15gb-878b5c33-dfm5
  3m		2m		8	{controller-manager }								Warning		FailedMount	Failed to attach volume "pvc-3ed3f856-0e1c-11e7-824a-42010af0012c" on node "[..]-pool-4cpu-15gb-878b5c33-dfm5" with: googleapi: Error 400: The disk resource '[...]-a-pvc-3ed3f856-0e1c-11e7-824a-42010af0012c' is already being used by '[...]-pool-4cpu-15gb-878b5c33-dm7r'
  2m		2m		1	{kubelet [...]-pool-4cpu-15gb-878b5c33-dfm5}			Warning		FailedMount	Unable to mount volumes for pod "postgres-1015904327-0cq7c_[...](6785daae-0ef2-11e7-824a-42010af0012c)": timeout expired waiting for volumes to attach/mount for pod "[...]"/"postgres-1015904327-0cq7c". list of unattached/unmounted volumes=[database-volume]
  2m		2m		1	{kubelet [...]-pool-4cpu-15gb-878b5c33-dfm5}			Warning		FailedSync	Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "[...]"/"postgres-1015904327-0cq7c". list of unattached/unmounted volumes=[database-volume]

It looks like it's a bug and is often related to a given node. It'd be nice to identify such "non-running" pods and their hosts, so we can probably quickly identify that one given node is not going well.

Supports users with limited permissions

When using RBAC'ed users, they may not be able to list the nodes or access aIl the namespaces. But we still want to be able to display the status of what they have access to.