Dejinta doorsoomayaasha deegaanka proxy ee Kubernetes Pod

Ku dheji doorsoomayaasha proxy HTTP ee la taageeray qeexitaanka container-ka Kubernetes oo u gaar yeel dariiqyada tooska ah ee cluster-ka iyo qaabeynta soo jiidashada sawirka.

Amar ku jira noodka Kubernetes ayaa isticmaali kara proxy shell halka Pod-ka noodkaas uusan lahayn deegaan proxy. Deegaanka container-ka waxaa qeexaya sawirkiisa iyo qaabeynta Pod.

Application taageera doorsoomayaashan, ku dar liis env gelitaanka container-ka ee jira:

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

Deployment gudihiisa, tani waxay ku hoos jirtaa container-ka ku habboon spec.template.spec.containers. Cusboonaysii culayska shaqada iyada oo loo marayo bandhigeeda caadiga ah si Pods cusub ay u helaan. Sidoo kale bixi magacyo xarfo yaryar marka macmiilka dhabta ah uu u baahan yahay.

Liiska dhaafka waa tusaale bilow ah, ma aha liis kasta oo dariiqo cluster ah. Isticmaal dhejiska DNS ee dhabta ah ee cluster-ka iyo meelaha gudaha. Applications isticmaala IP adeegga waxaa laga yaabaa inay u baahdaan xaddiga adeegga dhabta ah qaab macmiilkooda taageero.

Init containers waxay leeyihiin qeexitaanno container oo u gaar ah. Ku dar qaabeynta loogu talagalay halkaas marka ay sameeyaan soo dejinta dibadda. Soo dejinta HTTP ee dadweynaha, barta dhamaadka oo ka timid liiska proxy HTTP ayaa musharax u ah qiyamka deegaanka container-kan.

Soo jiidashada sawirka waxay dhacdaa ka hor inta application-ku uusan shaqeyn waxaana sameeya runtime container-ka noodka. Pod env ma qaabeyn karo xiriirka diiwaangelinta hore.

Ugu dambeyntii, doorsoomayaasha proxy HTTP waxay saameeyaan oo kaliya macaamiisha isticmaala. Ma leexiyaan taraafikada database, UDP ama socket kale oo aan loo baahnayn ee ka imanaya Pod.

Maqaallo la xiriira