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

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

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.

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
eck-operator_logs1919×641 135 KB

ECK Operator statefulset :
eck-operator-sts

Elasticsearch stays in init phase :

elastic-stay-init
elastic-stay-init869×198 28.2 KB

Using ECK 2.4

Thanks for help.

2

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

3

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