Skip to content

Commit 5c9995d

Browse files
hbelmiromprahl
andauthored
pipelines: Added proxy documentation (#4073)
* pipelines: Added proxy documentation Signed-off-by: Helber Belmiro <[email protected]> * Update content/en/docs/components/pipelines/operator-guides/server-config.md Co-authored-by: Matt Prahl <[email protected]> Signed-off-by: Helber Belmiro <[email protected]> * pipelines: Removed unneeded sections Signed-off-by: Helber Belmiro <[email protected]> --------- Signed-off-by: Helber Belmiro <[email protected]> Co-authored-by: Matt Prahl <[email protected]>
1 parent edee0de commit 5c9995d

File tree

1 file changed

+46
-1
lines changed

1 file changed

+46
-1
lines changed

content/en/docs/components/pipelines/operator-guides/server-config.md

+46-1
Original file line numberDiff line numberDiff line change
@@ -39,4 +39,49 @@ For full fledged Kubeflow, each namespace corresponds to a project with the same
3939
To configure the `ALLOWED_ARTIFACT_DOMAIN_REGEX` value for user namespace, add an entry in `ml-pipeline-ui-artifact`
4040
just like this example in [sync.py](https://github.com/kubeflow/pipelines/blob/b630d5c8ae7559be0011e67f01e3aec1946ef765/manifests/kustomize/base/installs/multi-user/pipelines-profile-controller/sync.py#L304-L310) for `ALLOWED_ARTIFACT_DOMAIN_REGEX` environment variable,
4141
the entry is identical to the environment variable instruction in Standalone Kubeflow Pipelines
42-
deployment.
42+
deployment.
43+
44+
## Proxy
45+
46+
Since KFP 2.5, you can set a server-scoped proxy configuration for the backend by setting any of the following environment variables (in uppercase) in the
47+
API Server deployment. All variables are optional.
48+
49+
- `HTTP_PROXY`
50+
- `HTTPS_PROXY`
51+
- `NO_PROXY`
52+
53+
If `HTTP_PROXY` or `HTTPS_PROXY` is set and `NO_PROXY` is not set, `NO_PROXY` will automatically be set to `localhost,127.0.0.1,.svc.cluster.local,kubernetes.default.svc,metadata-grpc-service,0,1,2,3,4,5,6,7,8,9`.
54+
55+
### Example of an API Server deployment with `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` set
56+
57+
```yaml
58+
apiVersion: apps/v1
59+
kind: Deployment
60+
metadata:
61+
labels:
62+
app: ml-pipeline
63+
application-crd-id: kubeflow-pipelines
64+
name: ml-pipeline
65+
namespace: kubeflow
66+
spec:
67+
selector:
68+
matchLabels:
69+
app: ml-pipeline
70+
application-crd-id: kubeflow-pipelines
71+
template:
72+
metadata:
73+
annotations:
74+
cluster-autoscaler.kubernetes.io/safe-to-evict: "true"
75+
labels:
76+
app: ml-pipeline
77+
application-crd-id: kubeflow-pipelines
78+
spec:
79+
containers:
80+
- env:
81+
- name: HTTP_PROXY
82+
value: http://squid.squid.svc.cluster.local:3128
83+
- name: HTTPS_PROXY
84+
value: http://squid.squid.svc.cluster.local:3128
85+
- name: NO_PROXY
86+
value: localhost,127.0.0.1,.svc.cluster.local,kubernetes.default.svc,metadata-grpc-service,0,1,2,3,4,5,6,7,8,9
87+
```

0 commit comments

Comments
 (0)