-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature/741/demo k3s #750
Feature/741/demo k3s #750
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.
just a comment on the canaryweight parameter of app-simplenode role when using ingress.mode canary
--- | ||
apiVersion: networking.k8s.io/v1 | ||
kind: Ingress | ||
metadata: | ||
annotations: | ||
kubernetes.io/ingress.class: "{{ .Values.ingress.class }}" | ||
nginx.ingress.kubernetes.io/canary: "{{ if .Values.ingress.isCanary }}true{{ else }}false{{ end }}" | ||
nginx.ingress.kubernetes.io/canary-weight: "{{ .Values.ingress.canaryWeight }}" |
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.
is "canaryWeight" redundant here? As I see, if the ingress.mode is "canary" this weight parameter is not used. weight is only 1 or 0
weighted: | ||
services: | ||
- name: {{ .Chart.Name }}-0 | ||
weight: 1 |
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 canaryWeight value be used here?
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.
For the nginx
ingress controller that is possible, but not for traefik
, as it requires a weighting for each target service. I wanted to keep backwards compatibility for those who are using microk8s
in combination with nginx
ingress.
Closes #741
Closes #739
Closes #643
Tested with the following use cases: