# ECK operator unable to apply azure client proxy parameters "azure.client.default.proxy.\*" to Elasticsearch

**URL:** <https://discuss.elastic.co/t/eck-operator-unable-to-apply-azure-client-proxy-parameters-azure-client-default-proxy-to-elasticsearch/380630>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [July 31, 2025, 11:29am UTC](https://discuss.elastic.co/t/eck-operator-unable-to-apply-azure-client-proxy-parameters-azure-client-default-proxy-to-elasticsearch/380630 "2025-07-31T11:29:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Verizon\_Bush](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/verizon_bush/32/144406_2.png) [@Verizon\_Bush](https://discuss.elastic.co/u/Verizon_Bush)\
**Post date:** [July 31, 2025, 11:29am UTC](https://discuss.elastic.co/t/eck-operator-unable-to-apply-azure-client-proxy-parameters-azure-client-default-proxy-to-elasticsearch/380630/1 "2025-07-31T11:29:27Z")

</div>

Deployed v3.1.0 ECK operator in OpenShift cluster.  
Provisioned a Elasticsearch cluster.  
Tried to configure Azure-repository plugin client proxy setting just like in the documentation:  
[Azure repository | Elasticsearch Guide [8.8] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.8/repository-azure.html)

This is my ealsticsearch.yaml:

```yaml
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: elasticsearch
  namespace: efk
spec:
  secureSettings:
  - secretName: az-secret
  version: 8.8.2
  http:
    tls:
      selfSignedCertificate:
        subjectAltNames:
          - dns: elasticsearch-int
          - dns: elasticsearch-int-es-default-0
          - dns: elasticsearch-int.efk-int.svc
          - dns: elasticsearch-int.efk-int.svc.cluster.local
          - dns: elasticsearch-int-es-default-0.efk.svc.cluster.local
          - dns: elasticsearch-int.my-domain.com
          - dns: elasticsearch-int.apps.cluster-name.my-domain.com
  nodeSets:
    - name: default
      count: 1
      config:
        xpack.security.ssl.diagnose.trust: true
        xpack.security.http.ssl.supported_protocols: ["TLSv1.2"]
        azure.client.default.proxy.host: my-proxy.domain.com
        azure.client.default.proxy.port: 1234
        azure.client.default.proxy.type: http
      podTemplate:
        spec:
          securityContext:
            fsGroup: 1000
          serviceAccountName: elastic-sa
          containers:
            - name: elasticsearch-container
              resources:
                requests:
                  memory: 6Gi
                  cpu: 500m
                limits:
                  memory: 6Gi
                  cpu: 500m
              env:
                - name: ES_JAVA_OPTS
                  value: -Xms5g -Xmx5g
          imagePullSecrets:
            - name: my-secrets
      volumeClaimTemplates:
        - metadata:
            name: elasticsearch-data
          spec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: 100Gi
            storageClassName: my-storage-class

```

But `ReconciliationComplete` Condition throws this error:

```json
{"error":"elasticsearch client failed for https://elasticsearch-es-default-0.elasticsearch-es-default.efk:9200/_internal/desired_nodes/a85006df-6b4e-4de1-b556-4fa8974d1515/3: 400 Bad Request: {Status:400 Error:{CausedBy:{Reason: Type:} Reason:Nodes with ids [elasticsearch-es-default-0] in positions [0] contain invalid settings Type:illegal_argument_exception StackTrace: RootCause:[{Reason:Nodes with ids [elasticsearch-es-default-0] in positions [0] contain invalid settings Type:illegal_argument_exception}]}}"}

```

And CRD elasticsearch gets tuck in _ApplyingChanges_ status.

This is after adding these parameters to the config:

```yaml
        azure.client.default.proxy.host: my-proxy.domain.com
        azure.client.default.proxy.port: 1234
        azure.client.default.proxy.type: http

```

Can't deploy any changes without these settings and without these settings my Azure blob storage repository doesn't work anymore.

Would greatly appreciate for any opinions, ideas how to overcome this!