Show PVC section
Closed this issue · 4 comments
kaplanelad commented
cregev commented
Here is the response Json:
{
"Cluster": "default",
"DeployBy": "foo@similarweb.com",
"ReportTo": [
"foo@similarweb.com",
"#foo-channel"
],
"Namespace": "default",
"Resources": {
"Daemonsets": {
},
"Deployments": {
},
"Statefulsets": {
"statefulset-0": {
"Pods": {
"statefulset-0-0": {
"Pvcs": {
"data-statefulset-0-0": [
{
"Time": 1582705470000000000,
"Action": "",
"Message": "waiting for a volume to be created, either by external provisioner \"k8s.io/minikube-hostpath\" or manually created by system administrator",
"ReportingController": ""
},
{
"Time": 1582705470000000000,
"Action": "",
"Message": "waiting for a volume to be created, either by external provisioner \"k8s.io/minikube-hostpath\" or manually created by system administrator",
"ReportingController": ""
},
{
"Time": 1582705470000000000,
"Action": "",
"Message": "External provisioner is provisioning volume for claim \"default/data-statefulset-0-0\"",
"ReportingController": ""
},
{
"Time": 1582705471000000000,
"Action": "",
"Message": "Successfully provisioned volume pvc-6a00853e-c617-4ce0-a61f-a49e502a7242",
"ReportingController": ""
}
]
},
"Phase": "Running",
"Events": [
{
"Time": 1582705452000000000,
"Action": "Scheduling",
"Message": "skip schedule deleting pod: default/statefulset-0-0",
"ReportingController": "default-scheduler"
},
{
"Time": 1582705470000000000,
"Action": "Scheduling",
"Message": "pod has unbound immediate PersistentVolumeClaims",
"ReportingController": "default-scheduler"
},
{
"Time": 1582705471000000000,
"Action": "Binding",
"Message": "Successfully assigned default/statefulset-0-0 to minikube",
"ReportingController": "default-scheduler"
},
{
"Time": 1582705471874977000,
"Action": "",
"Message": "ContainerCreating",
"ReportingController": ""
},
{
"Time": 1582705473000000000,
"Action": "",
"Message": "Container image \"nginx:latest\" already present on machine",
"ReportingController": ""
},
{
"Time": 1582705473000000000,
"Action": "",
"Message": "Created container statefulset-0",
"ReportingController": ""
},
{
"Time": 1582705473000000000,
"Action": "",
"Message": "Started container statefulset-0",
"ReportingController": ""
}
],
"CreationTimestamp": "0001-01-01T00:00:00Z"
}
},
"Events": null,
"Status": {
"replicas": 1,
"readyReplicas": 1,
"collisionCount": 0,
"updateRevision": "statefulset-0-598486f86c",
"currentReplicas": 1,
"currentRevision": "statefulset-0-598486f86c",
"updatedReplicas": 1,
"observedGeneration": 1
},
"MetaData": {
"Name": "statusbay-application",
"Alerts": [
{
"Tags": "nginx",
"Provider": "pingdom"
}
],
"Labels": {
},
"Metrics": [
{
"Name": "estatefulsetrrors 5xx",
"Query": "query for 5xx",
"Provider": "datadog"
},
{
"Name": "2xx",
"Query": "query for 2xx",
"Provider": "datadog"
}
],
"Namespace": "default",
"Annotations": {
"statusbay.io/alerts-pingdom": "nginx",
"statusbay.io/application-name": "statusbay-application",
"statusbay.io/report-deploy-by": "foo@similarweb.com",
"statusbay.io/metrics-datadog-2xx": "query for 2xx",
"statusbay.io/report-slack-channels": "#foo-channel",
"statusbay.io/progress-deadline-seconds": "30",
"statusbay.io/metrics-datadog-estatefulsetrrors-5xx": "query for 5xx"
},
"ClusterName": "",
"DesiredState": 1
},
"ProgressDeadlineSeconds": 30
}
}
},
"Application": "statusbay-application",
"CreationTimestamp": 1582705470,
"DeploymentDescription": "Deployment completed successfully"
}
cregev commented
Look at the section of the PVCS:
kaplanelad commented
@cregev, let talk on this issue on Sunday. we need to think what is the best way to show this event to the user
kaplanelad commented
@liorbd did you fixed the scroll issue?