If the deployment of your application is not successful, then debugging needs to be done to check the cause of the error.
This can be done through
App Details section which you can access in the following way:-
Over here, you can see the status of the app as Healthy. If there are some errors with deployment then the status would not be in a Healthy state.
Events of the application are accessible from the bottom left corner.
Events section displays you the events that took place during the deployment of an app. These events are available until 15 minutes of deployment of the application.
Logs contain the logs of the Pods and Containers deployed which you can use for the process of debugging.
The Manifest shows the critical information such as Container-image, restartCount, state, phase, podIP, startTime etc. and status of the pods deployed.
You might run into a situation where you need to delete Pods. You may need to bounce or restart a pod.
Deleting a Pod is not an irksome task, it can simply be deleted by Clicking on
Suppose you want to setup a new environment, you can delete a pod and thereafter a new pod will be created automatically depending upon the replica count.
You can view
Application Objects in this section of
App Details, such as:
ReplicaSet(ensures how many replica of pod should be running), Status of Pod(status of the Pod)
Service(an abstraction which defines a logical set of Pods), Endpoints(names of the endpoints that implement a Service), Ingress(API object that manages external access to the services in a cluster)
ConfigMap( API object used to store non-confidential data in key-value pairs)
Rollout(new Pods will be scheduled on Nodes with available resources), ServiceMonitor(specifies how groups of services should be monitored)
You can monitor the application in the
Metrics like CPU Usage, Memory Usage, Throughput and Latency can be viewed here.
Percentage of CPU's cycles used by the app.
Amount of memory used by app.
Performance of the app.
Delay caused while transmitting the data.