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.

Sign up for GitHub

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

Jump to bottom

Detect if the ingress controller is running with multiple replicas #579

Merged
merged 1 commit into from
Apr 9, 2017
Merged

Detect if the ingress controller is running with multiple replicas #579

merged 1 commit into from
Apr 9, 2017

Conversation

aledbf
Copy link
Member

@aledbf aledbf commented Apr 9, 2017

fixes #533

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Apr 9, 2017
@k8s-reviewable
Copy link

This change is Reviewable

@coveralls
Copy link

Coverage Status

Coverage increased (+0.03%) to 44.43% when pulling 5bd729a on aledbf:avoid-removing-status into 7f6aaf0 on kubernetes:master.

@aledbf aledbf merged commit 6ed6475 into kubernetes:master Apr 9, 2017
@aledbf aledbf deleted the avoid-removing-status branch May 20, 2017 22:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Deleting Ingress controller pod causes all ingress statuses to be wiped
4 participants
@aledbf @k8s-reviewable @coveralls @k8s-ci-robot