Settings for corporate proxy?

[empath]

/area networking

/kind doc

Expected Behavior

Sample app doesn't deploy on minikube running behind a corporate proxy. istio and all the serving pods download and install correctly, but deploying the sample app gives me this:

Status:
  Conditions:
    Last Transition Time:  2018-07-25T15:30:26Z
    Reason:                Deploying
    Status:                Unknown
    Type:                  ResourcesAvailable
    Last Transition Time:  2018-07-25T15:35:48Z
    Message:               Get https://gcr.io/v2/: dial tcp 173.194.204.82:443: i/o timeout
    Reason:                ContainerMissing
    Status:                False
    Type:                  ContainerHealthy
    Last Transition Time:  2018-07-25T15:35:48Z
    Message:               Get https://gcr.io/v2/: dial tcp 173.194.204.82:443: i/o timeout
    Reason:                ContainerMissing
    Status:                False
    Type:                  Ready
  Log URL:                 http://localhost:8001/api/v1/namespaces/monitoring/services/kibana-logging/proxy/app/kibana#/discover?_a=(query:(match:(kubernetes.labels.knative-dev%2FrevisionUID:(query:'a7b92dd3-901f-11e8-93b7-080027584828',type:phrase))))

Do some of the pods need proxy settings applied to them as env variables? I can't find anything referring to proxies in the docs or in the code in this repo.

[mattmoor]

I'm surprised that you can run the controllers, but that this fails (it looks like digest resolution, possibly of the sidecars?).

You can try disabling digest resolution to see if it helps via kubectl -n knative-serving edit configmap config-controller and add GCR to this list: https://github.com/knative/serving/blob/master/config/config-controller.yaml#L31

[cppforlife]

@empath did you install knative (https://github.com/knative/docs/blob/master/install/Knative-with-GKE.md#installing-knative-serving) without modifying release.yaml at all?

[zrss]

hi @empath. er, i have encoutered the same case. Finally i found that, as @mattmoor said, it's the problem about digest resolution, u can set the http proxy env in controller of the knative-serving to solve this problem

see this Knative http proxy sample for detail

[mattmoor]

cc @jonjohnsonjr

Related to digest resolution.

[jonjohnsonjr]

Going to fix this (and some other issues) by just updating the documentation, thanks @zrss for the pointer.

See knative/docs#1260

[jonjohnsonjr]

/close

[knative-prow-robot]

@jonjohnsonjr: Closing this issue.

Details

In response to this:

/close

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.