# Crash of ECK Operator after disabling TLS on elastic agent in fleet mode

**URL:** <https://discuss.elastic.co/t/crash-of-eck-operator-after-disabling-tls-on-elastic-agent-in-fleet-mode/315679>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [October 3, 2022, 10:52am UTC](https://discuss.elastic.co/t/crash-of-eck-operator-after-disabling-tls-on-elastic-agent-in-fleet-mode/315679 "2022-10-03T10:52:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![p0sql](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/p0sql/32/111612_2.png) [@p0sql](https://discuss.elastic.co/u/p0sql)\
**Post date:** [October 3, 2022, 10:52am UTC](https://discuss.elastic.co/t/crash-of-eck-operator-after-disabling-tls-on-elastic-agent-in-fleet-mode/315679/1 "2022-10-03T10:52:33Z")

</div>

Disable TLS on Fleet Server agent leads to **panic runtime error** (invalid memory address or nil pointer dereference) for the ECK Operator. I can't deploy anything after this crash until I delete the configuration.  
Moreover, I cannot use Fleet Server without TLS.

```auto
apiVersion: agent.k8s.elastic.co/v1alpha1
kind: Agent        
metadata:                                                                                                             
  name: fleet-server                 
  namespace: default
spec:
  version: 8.4.2
  kibanaRef:
    name: quickstart
  elasticsearchRefs:
  - name: quickstart
  http:
    tls:
      selfSignedCertificate:
        disabled: true
  mode: fleet
  fleetServerEnabled: true
  deployment:
    replicas: 1
    podTemplate:
      spec:
        serviceAccountName: elastic-agent
        automountServiceAccountToken: true
        securityContext:
          runAsUser: 0

```

ECK Operator logs :

 ![eck-operator_logs](https://us1.discourse-cdn.com/elastic/original/3X/2/8/2883c331c63a93861a6d60c68c4ccd756ad63e69.png)

ECK Operator statefulset :  
 ![eck-operator-sts](https://us1.discourse-cdn.com/elastic/original/3X/7/a/7acfc6f1eee7cc11b388a60b266de24225bf0e41.png)

Elasticsearch stays in init phase :

 ![elastic-stay-init](https://us1.discourse-cdn.com/elastic/original/3X/0/9/09cf8454e34d842e4b43ec263227ba5cb75027b1.png)

Using ECK 2.4

Thanks for help.

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [October 3, 2022, 2:04pm UTC](https://discuss.elastic.co/t/crash-of-eck-operator-after-disabling-tls-on-elastic-agent-in-fleet-mode/315679/2 "2022-10-03T14:04:52Z")

</div>

Hey @p0sql we are aware of that issue. There is unfortunately currently no workaround, sorry about that. However a fix is in the works [Allow Fleet Server to be run without TLS. by naemono · Pull Request #6020 · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/pull/6020)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 31, 2022, 2:05pm UTC](https://discuss.elastic.co/t/crash-of-eck-operator-after-disabling-tls-on-elastic-agent-in-fleet-mode/315679/3 "2022-10-31T14:05:46Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.