Expose REGISTRY_HTTP_CLIENT_TIMEOUT via Helm Values for Registry Deployment

[Ronifr-git]

Context

Our current deployments operate in restricted, high-latency, and low-bandwidth network environments. During operations such as proxy-caching or large image pulls from upstream registries, we are observing frequent failures.

Problem:

The Harbor Registry component uses a hardcoded default of 30 seconds for its internal HTTP client timeout. In our specific network conditions, this window is insufficient, leading to context canceled or timeout errors during the proxy-cache process.

Proposed Solution:

Introduce a configurable parameter in the values.yaml to allow for the dynamic setting of the REGISTRY_HTTP_CLIENT_TIMEOUT environment variable within the Registry deployment template.

Proposed Key: registry.httpClientTimeout

Default Value: 30

Implementation: Inject the value into the registry deployment container spec as an environment variable.

[smitphilip]

i would image this is possible via the extraEnvVars parameter:

    registry:
      resources:
        requests:
          memory: 512Mi
          cpu: 200m
        limits:
          memory: 512Mi
          cpu: 500m
      extraEnvVars:
      - name: REGISTRY_HTTP_CLIENT_TIMEOUT
        value: "300s"

but this isn't working for me

[smitphilip]

um. so... the issue seems to be with this line: (no issue, I misunderstood the config)
https://github.com/goharbor/harbor-helm/blob/main/templates/registry/registry-dpl.yaml#L173

    registry:
      resources:
        requests:
          memory: 512Mi
          cpu: 200m
        limits:
          memory: 512Mi
          cpu: 500m
      registry:
        extraEnvVars:
        - name: REGISTRY_HTTP_CLIENT_TIMEOUT
          value: "300s"

the above is working:

> k exec -it harbor-registry-5c8689b46-fpjh9 -c registry -- printenv | grep -i timeout
REGISTRY_HTTP_CLIENT_TIMEOUT=300s

[Ronifr-git]

This is what I ended up doing, but I'd prefer it to be a configurable field via values.yaml and not have to edit the deployment file.

[smitphilip]

I'm not following... this is via the values file?

    registry:
      resources:
        requests:
          memory: 512Mi
          cpu: 200m
        limits:
          memory: 512Mi
          cpu: 500m
      registry:
        extraEnvVars:
        - name: REGISTRY_HTTP_CLIENT_TIMEOUT
          value: "300s"