Yi amfani da Secret da ke akwai don masu canza proxy a cikin taswirar Helm

Ka ɗauka cewa namespace na fitarwar yana da Secret mai suna app-outbound-proxy tuni. Maɓallansa http_proxy da https_proxy suna ɗauke da cikakkun URL na proxy da manhajar ke buƙata.

Taswirar Helm 3 za ta iya ajiye sunan wannan Secret kawai a cikin values.yaml:

outboundProxy:
  existingSecret: app-outbound-proxy

A cikin samfurin Deployment na kwantenar da ake nufi, yi nuni da maɓallan:

env:
  - name: HTTP_PROXY
    valueFrom:
      secretKeyRef:
        name: {{ .Values.outboundProxy.existingSecret | quote }}
        key: http_proxy
  - name: HTTPS_PROXY
    valueFrom:
      secretKeyRef:
        name: {{ .Values.outboundProxy.existingSecret | quote }}
        key: https_proxy

Wannan yanki ne na ƙayyadaddun kwantena. Dole Secret ya kasance a cikin namespace na Pod kuma ya ƙunshi duka maɓallan da aka ambata. Ƙimominsa dole su yi amfani da ka'ida, mai masauki da tashar jiragen ruwa na ainihin mai sauraron proxy. Don buƙatun jama'a na manhajar da aka ba su izinin amfani da proxy na jama'a ba tare da tabbatarwa ba, gina waɗannan URL daga ɗan takara da ya dace a cikin jerin proxy na kyauta; riƙe duk wani keɓancewar kai tsaye da ake buƙata.

Ƙimar taswirar tana ba da suna; secretKeyRef yana ba da ƙimomin muhallin kwantena. Yin export ɗin HTTP_PROXY kawai a cikin shell da ke gudanar da helm ba ya ƙara wannan sashen env a cikin samfurin Pod.

Canza Secret canjin zagayowar rayuwa ne kuma

Kwantiya ba ya sabunta muhallinsa lokacin da bayanan Secret suka canza. Shirya sake farawa ko rollout ɗin da ake nufi domin sabbin kwantenan da aka fara su karɓi sabbin ƙimomi. Canza bayanai ƙarƙashin sunan Secret ɗaya ba ya gyara samfurin Pod na Deployment shi kaɗai.

Dole manhajar ta goyi bayan masu canza muhallin proxy da aka zaɓa. Shiga ma'ajiyar Helm da jawo hoton node masu amfani ne daban waɗanda ke gudana kafin wannan muhallin kwantena ya iya taimakawa.