-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Conversation
Hi @mgoodness. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@mgoodness This looks great! I'd be happy to stay on as the maintainer! 😉 It's much better as two charts. I'll pull this down and give it a test. |
Tested this over the weekend without any issues. Will wait for @jackzampolin to give the LGTM |
ping @jackzampolin, does this have your LGTM? |
@bacongobbler Got to this today. LGTM. Sorry for the delay there. |
This is the first time we're changing the name/deprecating a chart, since nginx-lego will stay in the repo, is there something we can do to let people know it's deprecated? e.g. we could push a final version that explains it's moved to nginx-ingress in the NOTES.txt? |
@prydonius I don't know how many users it had. In this particular case there was an issue (my b) with the other chart that prevented it from deploying successfully. It would be nice to do in the future but I think it might be overkill for this particular instance. |
I ran into a small hiccup in regards to the instructions.
```
services:
- name: controller
# annotations:
type: NodePort
```
~~So after I created my ingress, I queried it and it appear to has the correct external facing ip.~~
Update below. |
Update: I mispoke. The problem for me was
should be
so status.addresses[1]
# instead of status.addresses[0] |
@jason-riddle it appears that a lot of charts use this in their NOTES, can you create a separate issue for it? |
sure |
Hey @mgoodness - I've just opened #540, and then gone on to spot this PR :) You seem to have put more into documenting so think it's best we stick with your PR, but may I request you add support for TCP & UDP configmaps into yours too? You can see an example of how I've done it in the above linked PR. I'm happy to do it myself, but will need to wait until after this has merged if so! |
@k8s-bot e2e test this |
@@ -0,0 +1,29 @@ | |||
{{- $root := . -}} | |||
{{- range .Values.controller.services }} | |||
--- |
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.
Tests are failing because of this. Do we have to loop in this file? When would I have multiple? Can we start with this hardcoded to 1 service?
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.
My specific use-case is to have the same nginx-ingress controllers exposed via two different ELBs (one internet-facing and one VPC-internal). But now that I think about it, that shouldn't be strictly necessary. I'll play with it over the weekend.
After further discussion with @prydonius, we've decided not to delete nginx-lego as part of this PR. Instead, I'll create another in which the README and NOTES.txt make it clear that it's been deprecated. There's also work planned in the Helm project to support/enforce deprecation. |
stable/nginx-ingress/Chart.yaml
Outdated
name: nginx-ingress | ||
version: 0.3.0 | ||
description: An nginx Ingress controller that uses ConfigMap to store the nginx configuration. | ||
keywords: |
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.
Can we add an icon here? e.g. pointing to https://cdn.wp.nginx.com/wp-content/themes/nginx-theme/assets/img/logo.png?
stable/nginx-ingress/README.md
Outdated
`controller.stats.service.externalIPs` | controller service stats external IP addresses | `[]` | ||
`controller.stats.service.loadBalancerIP` | IP address to assign to load balancer (if supported) | `""` | ||
`controller.stats.service.loadBalancerSourceRanges` | list of IP CIDRs allowed access to load balancer (if supported) | `[]` | ||
`controller.service.type` | type of controller stats service to create | `ClusterIP` |
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.
should this be controller.stats.service.type
?
stable/nginx-ingress/README.md
Outdated
`defaultBackend.service.externalIPs` | default backend service external IP addresses | `[]` | ||
`defaultBackend.service.loadBalancerIP` | IP address to assign to load balancer (if supported) | `""` | ||
`defaultBackend.service.loadBalancerSourceRanges` | list of IP CIDRs allowed access to load balancer (if supported) | `[]` | ||
`controller.service.type` | type of default backend service to create | `ClusterIP` |
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.
defaultBackend.service.type?
@mgoodness just some small fixes in the README, otherwise this lgtm! |
This is a stand-alone chart for the nginx ingress controller that, along with the kube-lego chart (#397), replaces nginx-lego. As mentioned and (briefly) discussed in #385.
@jackzampolin