-
Notifications
You must be signed in to change notification settings - Fork 669
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
MF-378 - Add nginx ingress config to k8s services #472
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #472 +/- ##
=======================================
Coverage 87.52% 87.52%
=======================================
Files 54 54
Lines 2372 2372
=======================================
Hits 2076 2076
Misses 194 194
Partials 102 102 Continue to review full report at Codecov.
|
Update README in accordance to latest changes. Add gRPC load balancing setup. Add healthcheck to k8s setup. Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Update README in accordance to latest changes. Add gRPC load balancing setup. Add healthcheck to k8s setup. Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>
Update README in accordance to latest changes. Add gRPC load balancing setup. Add healthcheck to k8s setup. Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>
Update README in accordance to latest changes. Add gRPC load balancing setup. Add healthcheck to k8s setup. Signed-off-by: Aleksandar Novakovic <aleksandar.novakovic@mainflux.com>
What does this do?
Adds nginx ingress and istio setup to k8s setup. Also added automatic rescaling.
Which issue(s) does this PR fix/relate to?
This PR resolves #378, #387 and #390.
List any changes that modify/break current functionality
Added prefixes to k8s services.
Have you included tests for your changes?
No.
Did you document any new/modified functionality?
Updated README file for k8s setup.