Kubernetes : Monitoring ,Logging, Debugging, Troubleshooting

  Kubernetes Pod logs

  Kubectl logs <<Pod Name>>

To find the Kubernetes cluster events

  Kubectl events


Docker logs

docker logs <<container name>>

To find the events occurred in docker daemon

docker events -- since <<date>>

Monitoring

Use Metric server implementation to monitor how much memory and CPU utilization for a particular pod or worker node.

There are other 3rd party tools are also available for monitoring ( Prometheus and Garfana)

Debugging and Troubleshooting

1. If the Pod is not getting created successfully then run kubectl describe pod <<podname>> command to check the events which are occured to created the pod and also check the properties of the pod in case you are getting unexpected value of any attribute

2. If you want to remove a pod under Replication controller or Deployment or a Service then run kubectl get pods -o wide command and identify the pod which is required to be deleted and delete with the help of kubectl delete pod <<pod name>> command

3. If a Pod is in running state but not working as per expected result, In that case check the log entries of the Pod

4. If a Pod is in the Pending state for a long time, In that case, check the worker node statuses by using kubectl get nodes command and check all nodes are in Ready State or not

5. If a Pod is not getting created on a particular node. In that case, check the node is tainted or not.

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more