Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/gocd] add host in template ingress.yaml instead of using default backend #10983

Merged
merged 2 commits into from
Jan 31, 2019
Merged

Conversation

colachg
Copy link
Contributor

@colachg colachg commented Jan 30, 2019

What this PR does / why we need it:

if there is no host in template ingress.yaml, use default backend.

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • DCO signed
  • Chart Version bumped
  • Variables are documented in the README.md

@helm-bot helm-bot added Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 30, 2019
@colachg
Copy link
Contributor Author

colachg commented Jan 30, 2019

@arvindsv @varshavaradarajan
I have deleted my repo and re-fork the helm/charts, the PR #10795 was closed. So I open this PR.
@sheroy
I take your advice using the default backend if there is no hosts in values.yaml. I have tested in minikube. Maybe you can do me a favor to test this on GKE :).

@sheroy
Copy link
Contributor

sheroy commented Jan 30, 2019

@colachg Sure, I'll test it today.

@arvindsv
Copy link
Collaborator

@colachg Just for the record, this is different from my recommendation mentioned here. The difference being that it's not backwards compatible with what exists today.

In case you have an ingress host name defined, you can't reach the server through the ingress IP any more. The Default Backend mentioned in the k8s docs will not be used (since one won't be defined, after this change).

I'm not saying that's necessarily wrong. Maybe that is how it is used and you should be expected to only use ingress hosts. I just don't know what it is that people use.

What I like, though, is that with no change made to values.yaml (assuming you had no hosts defined), then the behavior is unchanged and the default backend is still defined and usable.

@arvindsv
Copy link
Collaborator

Maybe @MPV, @balboah and others who've contributed to this chart have thoughts / ideas?

@colachg
Copy link
Contributor Author

colachg commented Jan 31, 2019

@arvindsv Thanks for your time :)

What I like, though, is that with no change made to values.yaml (assuming you had no hosts defined), then the behavior is unchanged and the default backend is still defined and usable.

Yes, the hosts in values are commented out, So the default backend works.
Then if somebody uncomments the hosts (s)he should know what will happen, maybe we can add some explains in comments.

@MPV
Copy link
Contributor

MPV commented Jan 31, 2019

Sorry @arvindsv, we have only spun up mainly agents with this chart so far. Soon looking to migrate our server into Kube too, but I'm not sure I have much input here yet.

Also, I only see the exact change described in this PR, and not much context on why this is needed.

@varshavaradarajan
Copy link
Collaborator

@MPV - more context: #10750 and #10795 if you're interested.

@MPV
Copy link
Contributor

MPV commented Jan 31, 2019

To me, the change makes sense in a general sense (supporting Traefik).

I can't speak to the regard how others use the ingress (by IP/hostname) though, sorry.

@arvindsv
Copy link
Collaborator

@MPV No worries. Thanks for taking a look and thinking about it.

@arvindsv
Copy link
Collaborator

/ok-to-test

@arvindsv
Copy link
Collaborator

/approve

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 31, 2019
@arvindsv
Copy link
Collaborator

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 31, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arvindsv, colachg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit f672cf7 into helm:master Jan 31, 2019
syedimam0012 pushed a commit to syedimam0012/charts that referenced this pull request Feb 1, 2019
…ult backend (helm#10983)

* if there is no host in template ingress.yaml, use default backend

Signed-off-by: cola <[email protected]>

* Update CHANGELOG

Signed-off-by: cola <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. Contribution Allowed If the contributor has signed the DCO or the CNCF CLA (prior to the move to a DCO). lgtm Indicates that a PR is ready to be merged. ok-to-test size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[stable/gocd] GoCD Ingress default template
7 participants