Namespace status conditions

[wozniakjan]

What this PR does / why we need it:
Add metrics for namespace status conditions - kubernetes/community#4045, kubernetes/kubernetes#73405

NOTE: this requires kubernetes v1.16 among dependencies. There is a tracker which updates the dependencies #945 and this PR should wait and rebase when #945 merges. As a makeshift solution for testing, this uses fork of autoscaler https://github.com/wozniakjan/autoscaler with swapped go dep to go mod and includes necessary changes to bring kubernetes v1.16.1 as a dependency. I will try to upstream the changes to autoscaler to unblock dependency mismatch. 7a75a4a contains the dependency update mentioned in #945

Sample output:

$ k get ns
NAME              STATUS        AGE
default           Active        3d5h
kube-node-lease   Active        3d5h
kube-public       Active        3d5h
kube-system       Active        3d5h
test              Terminating   3d5h

$ curl localhost:8080/metrics | grep namespace_status
# HELP kube_namespace_status_phase kubernetes namespace status phase.
# TYPE kube_namespace_status_phase gauge
kube_namespace_status_phase{namespace="kube-node-lease",phase="Active"} 1
kube_namespace_status_phase{namespace="kube-node-lease",phase="Terminating"} 0
kube_namespace_status_phase{namespace="default",phase="Active"} 1
kube_namespace_status_phase{namespace="default",phase="Terminating"} 0
kube_namespace_status_phase{namespace="test",phase="Active"} 0
kube_namespace_status_phase{namespace="test",phase="Terminating"} 1
kube_namespace_status_phase{namespace="kube-system",phase="Active"} 1
kube_namespace_status_phase{namespace="kube-system",phase="Terminating"} 0
kube_namespace_status_phase{namespace="kube-public",phase="Active"} 1
kube_namespace_status_phase{namespace="kube-public",phase="Terminating"} 0
# HELP kube_namespace_status_condition The condition of a namespace.
# TYPE kube_namespace_status_condition gauge
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionDiscoveryFailure",status="true"} 1
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionDiscoveryFailure",status="false"} 0
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionDiscoveryFailure",status="unknown"} 0
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionGroupVersionParsingFailure",status="true"} 0
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionGroupVersionParsingFailure",status="false"} 1
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionGroupVersionParsingFailure",status="unknown"} 0
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionContentFailure",status="true"} 0
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionContentFailure",status="false"} 1
kube_namespace_status_condition{namespace="test",condition="NamespaceDeletionContentFailure",status="unknown"} 0

[tariq1890]

Thanks @wozniakjan! I've also created this issue on the autoscaler repository - kubernetes/autoscaler#2447

[lilic]

Thanks for your PR. Do you mind also adding this to the docs, thanks!

[wozniakjan]

@tariq1890, @brennerm the VPA has now updated the deps kubernetes/autoscaler#2486

In 7a75a4a I tried to update the go modules with updated VPA. This was the smallest set of changes allowed me to build the kube-state-metrics, any hints and pointers on how to make it even smaller so I don't pollute the go.mod file are greatly appreciated. The reason for the replace directives is VPA now comes with go.mod that comes with set of changes requiring the replacements kubernetes/autoscaler#2486, kubernetes/kubernetes#79384

[lilic]

This is looking good to me, are we ready to move forward with this PR?

cc @tariq1890 to re-review as well

[tariq1890]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tariq1890, wozniakjan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tariq1890]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tariq1890]

@wozniakjan Thank you so much for your hard work with this! You are awesome :).

[wozniakjan]

Thanks for valuable feedback and reviewing this to successful merge, always happy to help :)