We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
I'm running kubernetes 1.6.7 which create that kind of PDB response:
{ "metadata": { "name": "myapp", "namespace": "mynamespace", "generation": 1, "creationTimestamp": "2018-02-14T10:04:15Z" }, "spec": { "minAvailable": "100%", "selector": { "matchLabels": { "app": "pyapp", "release": "pyrelease" } } }, "status": { "observedGeneration": 1, "disruptedPods": null, "disruptionsAllowed": 0, "currentHealthy": 0, "desiredHealthy": 0, "expectedPods": 0 } },
Then, I encounter an error while using the documentation sample: https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/PolicyV1beta1Api.md#list_pod_disruption_budget_for_all_namespaces
In fact, V1beta1PodDisruptionBudgetStatus instance initialization can't have a null/None value.
The text was updated successfully, but these errors were encountered:
dup of #376
Sorry, something went wrong.
No branches or pull requests
I'm running kubernetes 1.6.7 which create that kind of PDB response:
Then, I encounter an error while using the documentation sample:
https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/PolicyV1beta1Api.md#list_pod_disruption_budget_for_all_namespaces
In fact, V1beta1PodDisruptionBudgetStatus instance initialization can't have a null/None value.
The text was updated successfully, but these errors were encountered: