-
Notifications
You must be signed in to change notification settings - Fork 234
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
Disable serviceLinks #3742
Disable serviceLinks #3742
Conversation
6099958
to
0bffd98
Compare
I approve @uthark - but just wondering could this break someone's current workflow/deployment I wonder? If it does, I would strongly advise the owners of the project in the question to avoid using these env vars - but still, might be a breaking change? |
yeah, please update risks ... sounds like we have to first find out who uses this to disable or only turn on in staging somehow |
It might break, so we need to announce the change and ask people to explicitly set the flag if they rely on this behavior. |
Turning on in staging sounds like a good idea no? It should shake out any deployments that fail - of course you need to deploy them first to find out! The vars do have a fairly predictable pattern - could grep GitHub?
|
we could do some opa rule that says "values must be set to either
true/false", but that would fail almost all deploys ... so maybe do that
after this rollout
for now only setting it on non-production sounds good, I'm still expecting
fallout since we at least use the kubernetes ports somewhere ...
…On Wed, Mar 4, 2020 at 5:36 PM Peter Mescalchin ***@***.***> wrote:
Turning on in staging sounds like a good idea no? It should shake out any
deployments that fail - of course you need to deploy them first to find
out! The vars do have a fairly predictable pattern - could grep GitHub?
DB_NAME=/web2/db
DB_PORT=tcp://172.17.0.5:5432
DB_PORT_5432_TCP=tcp://172.17.0.5:5432
DB_PORT_5432_TCP_PROTO=tcp
DB_PORT_5432_TCP_PORT=5432
DB_PORT_5432_TCP_ADDR=172.17.0.5
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#3742?email_source=notifications&email_token=AAACYZYCYSUZ2ZUGIPZAUTLRF36ZZA5CNFSM4LB7TJRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEN3LGLY#issuecomment-594981679>, or
unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACYZZ5M7QFH7IJR5O5A73RF36ZZANCNFSM4LB7TJRA>.
|
@@ -267,6 +269,11 @@ def set_history_limit | |||
template[:spec][:revisionHistoryLimit] ||= 1 | |||
end | |||
|
|||
# disable service links. | |||
def set_disable_service_links | |||
template[:spec][:template][:spec][:enableServiceLinks] ||= false |
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.
we should set that on pod_templates for consistency, not only Deployments, use pod_template
To not pollute env of the containers, disable serviceLinks by default.
If the deployment explicitly has it, keep as is.
Some back story:
--links
- what causes this.Risks