Umyalo ku-node ye-Kubernetes ungasebenzisa i-shell proxy kuyilapho i-Pod kuleyo node ingenayo i-proxy environment. I-environment ye-container ichazwa yi-image yayo kanye ne-Pod configuration.

Nge-application esekela la ma-variables, faka uhlu lwe-env ku-container entry ekhona:

env:
  - name: HTTP_PROXY
    value: http://proxy.example:8080
  - name: HTTPS_PROXY
    value: http://proxy.example:8080
  - name: NO_PROXY
    value: localhost,127.0.0.1,kubernetes.default.svc,.svc,.cluster.local

Ku-Deployment, lokhu kungaphansi kwe-container efanele ku-spec.template.spec.containers. Buyekeza i-workload ngokusebenzisa i-rollout yayo evamile ukuze ama-Pod amasha ayithole. Nikeza namagama anezinhlamvu ezincane uma iklayenti langempela likufuna.

Uhlu lokweqa luyisibonelo sokuqala, hhayi uhlu lwazo zonke izindlela ku-cluster. Sebenzisa i-DNS suffix yangempela ye-cluster kanye nezindawo zangaphakathi. Ama-application asebenzisa ama-IP esevisi angase adinge izigaba zesevisi zangempela ku-syntax esekelwa iklayenti lawo.

Ama-container e-init anezincazelo zawo zekhontheyna. Faka ukucushwa okuhloswe lapho lapho enza ukulandwa kwangaphandle. Ngokulandwa kwe-HTTP komphakathi, i-endpoint evela ohlelweni lwama-proxy e-HTTP ingumgadli wala mavelu e-environment yekhontheyna.

Ukudonswa kwezithombe kwenzeka ngaphambi kokuba i-application isebenze futhi kwenziwa yi-runtime yekhontheyna ye-node. I-Pod env ayikwazi ukucubungula lokho kuxhumana kwangaphambilini kwerejista.

Ekugcineni, ama-proxy variables e-HTTP athinta kuphela amaklayenti asebenzisa wona. Awaqondisi kabusha noma yikuphi ukuhamba kwedatha yedatha, i-UDP noma enye isokhethi evela ku-Pod.

Izihloko ezihlobene