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

Report ingress status #325

Merged
merged 3 commits into from
Aug 1, 2018
Merged

Report ingress status #325

merged 3 commits into from
Aug 1, 2018

Conversation

isaachawley
Copy link
Contributor

@isaachawley isaachawley commented Jul 27, 2018

Update the address field in the status of Ingresses resources. The source for the status address can be a service of type LoadBalancer, or a config map key specifying the address to report.

New command-line arguments: report-ingress-status, external-service, and enable-leader-election.
New config map key: external-status-address.

Uses Leader Election, if enabled, to avoid multiple Ingress controllers attempting to update ingress status.

Fixes the following issues:

Checklist

Before creating a PR, run through this checklist and mark each as complete.

  • I have read the CONTRIBUTING doc
  • I have checked that all unit tests pass after adding my changes
  • I have updated necessary documentation
  • I have rebased my branch onto master
  • I will ensure my PR is targeting the master branch and pulling from my branch from my own fork

isaachawley and others added 2 commits July 27, 2018 09:06
Update the address field in the status of Ingresses resources. The source for the external status can be a service of type LoadBalancer, or a config map key specifying the address to report.

New command-line arguments: report-ingress-status, external-service string, and enable-leader-election.
New config map key: external-status-address.

Uses Leader Election, if enabled, to avoid multiple Ingress controllers attempting to update ingress status.
@isaachawley isaachawley added the enhancement Pull requests for new features/feature enhancements label Jul 27, 2018
@isaachawley isaachawley self-assigned this Jul 27, 2018
Copy link
Contributor

@pleshakov pleshakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional problems:

  • every 30s, I0727 22:08:04.748471 1 controller.go:214] Ingress cafe-ingress changed, syncing That leads to a configuration reload

}

// UpdateManagedAndMergeableIngresses handles the full return format of LoadBalancerController.getManagedIngresses
func (su *StatusUpdater) UpdateManagedAndMergeableIngresses(managedIngresses []v1beta1.Ingress, mExes map[string]*nginx.MergeableIngresses) error {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mExes is a weird name

- Was ignoring changed Ingresses instead of unchanged
- Change names of mExes to mergableIngExes
@isserrano
Copy link
Contributor

Ignore the jenkins check for this one

1 similar comment
@isserrano
Copy link
Contributor

Ignore the jenkins check for this one

@isaachawley isaachawley merged commit a552bd0 into master Aug 1, 2018
@isaachawley isaachawley deleted the report-ingress-status branch August 1, 2018 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Pull requests for new features/feature enhancements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants