Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deployment: skip max unavailable if rolling update is unset #86

Merged
merged 1 commit into from
Feb 10, 2017

Conversation

brancz
Copy link
Member

@brancz brancz commented Feb 10, 2017

This previously caused panics when objects did not have the
RollingUpdate struct set.

I also validated, that the tests would now also panic, without the fix.

Closes #84. I'll create a patch release with this once the fix is merged.

@alexsomesan @fabxc

/cc @rvrignaud @stvnwrgs


This change is Reviewable

This previously caused panics when objects did not have the
RollingUpdate struct set.
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 10, 2017
@fabxc
Copy link
Contributor

fabxc commented Feb 10, 2017

👍

@fabxc fabxc merged commit 5ee8709 into kubernetes:master Feb 10, 2017
@brancz brancz deleted the fix-deployment-panic branch February 10, 2017 23:22
while1malloc0 pushed a commit to while1malloc0/kube-state-metrics that referenced this pull request Jul 2, 2018
deployment: skip max unavailable if rolling update is unset
rexagod pushed a commit to rexagod/kube-state-metrics that referenced this pull request Oct 16, 2023
…ry-pick-85-to-release-4.10

[release-4.10] OCPBUGS-4086: cherry-pick, do not expose ingress path metric when service is nil
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Panic runtime error for 0.4.0 in GKE 1.5.2
4 participants