Nginx ingress #104
Merged
Nginx ingress #104
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
databus23
approved these changes
Nov 20, 2017
| name: controller | ||
| image: | ||
| repository: gcr.io/google_containers/nginx-ingress-controller | ||
| tag: "0.9.0-beta.14" |
There was a problem hiding this comment.
Any reason we are not using latest (beta.17)?
There was a problem hiding this comment.
Right. I'll test in staging first and update this PR afterwards
auhlig
force-pushed
the
nginx-ingress
branch
3 times, most recently
from
c0557ac to
e2c629d
Compare
|
Squashed, rebased and manually deployed to |
auhlig
force-pushed
the
nginx-ingress
branch
from
e2c629d to
4bcdc17
Compare
|
Wanted to test the new controller in staging first, but it's a mess since they changed all nginx-based annotations :-/ Should be easier to get it in here. |
auhlig
force-pushed
the
nginx-ingress
branch
from
4bcdc17 to
2615016
Compare
auhlig
force-pushed
the
nginx-ingress
branch
from
2615016 to
6c3032e
Compare
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.
we want the ingress custom backend is already deployed in the admin cluster in the kubernikus control plane.
official helm chart for nginx-ingress as base but with custom backend that also knows json. fixes #80.
Initially I wanted to use it as a dependency but override the image of the custom backend, but that doesn't seem to work.