forked from uswitch/yggdrasil
-
Notifications
You must be signed in to change notification settings - Fork 0
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
All changements to merge #4
Open
Lowaiz
wants to merge
28
commits into
master
Choose a base branch
from
staging
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Laurent Marchaud <[email protected]>
The new annotations got the priority, the simple 'timeout' annotation still sets the 3 timeouts but if there is, at least one of the new ones, it's overwriting the values set by the simple annotation.
Applying @Aluxima suggestion Co-authored-by: Laurent Marchaud <[email protected]>
Signed-off-by: Laurent Marchaud <[email protected]>
Signed-off-by: Laurent Marchaud <[email protected]>
Signed-off-by: Laurent Marchaud <[email protected]>
… domain different than the our ingress
Signed-off-by: Laurent Marchaud <[email protected]>
* remove healthcheck for bad configure ingress with wildcard * fix: reorder code for a more comprehensive way
* remove healthcheck for bad configure ingress with wildcard * feat: add a way to configure log path
Signed-off-by: Laurent Marchaud <[email protected]>
* Add a feature to handle maintenance mode on yggdrasil * Add a metrics with upstream informations to join with kube ingress metrics
…ctly from the metrics
fix(metrics): be aware when an ingress is deleted and remove it corre…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.