Kibana and Fleet setup failed unable to authenticate user

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Im trying to setup kibana and fleet uisng the following example. https://github.com/elastic/cloud-on-k8s/blob/main/config/recipes/elastic-agent/fleet-kubernetes-integration.yaml

However kibana is giving me the following error:

[2022-05-10T08:51:45.939+00:00][INFO ][http.server.Kibana] http server
running at https://0.0.0.0:5601 [2022-05-10T08:51:45.964+00:00][WARN
][environment] Detected an unhandled Promise rejection: ResponseError:
unable to authenticate user [elastic-system-kibana-prod-kibana-user]
for REST request
[/.kibana_task_manager_8.2.0/_doc/task%3Adata_enhanced_search_sessions_cleanup?refresh=wait_for]:
security_exception: [security_exception] Reason: unable to
authenticate user [elastic-system-kibana-prod-kibana-user] for REST
request
[/.kibana_task_manager_8.2.0/_doc/task%3Adata_enhanced_search_sessions_cleanup?refresh=wait_for]
at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:476:27)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at KibanaTransport.request (/usr/share/kibana/src/core/server/elasticsearch/client/create_transport.js:58:16)
at ClientTraced.DeleteApi [as delete] (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/delete.js:36:12)
[2022-05-10T08:51:46.088+00:00][INFO ][status] Kibana is now critical
[2022-05-10T08:51:46.099+00:00][WARN ][environment] Detected an
unhandled Promise rejection: ResponseError: unable to authenticate
user [elastic-system-kibana-prod-kibana-user] for REST request
[/.kibana_8.2.0/_search?rest_total_hits_as_int=true]:
security_exception: [security_exception] Reason: unable to
authenticate user [elastic-system-kibana-prod-kibana-user] for REST
request [/.kibana_8.2.0/_search?rest_total_hits_as_int=true]
at KibanaTransport.request (/usr/share/kibana/node_modules/@elastic/transport/lib/Transport.js:476:27)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at KibanaTransport.request (/usr/share/kibana/src/core/server/elasticsearch/client/create_transport.js:58:16)
at ClientTraced.SearchApi [as search] (/usr/share/kibana/node_modules/@elastic/elasticsearch/lib/api/api/search.js:65:12)

kibana.yml

apiVersion: kibana.k8s.elastic.co/v1
kind: Kibana
metadata:
  name: kibana-prod
  namespace: elastic-system
spec:
  version: 8.2.0
  count: 1
  elasticsearchRef:
    name: elasticsearch-prod
  config:
    xpack.fleet.agents.elasticsearch.hosts: ["https://elasticsearch-prod-es-http.elastic-system.svc:9200"]
    xpack.fleet.agents.fleet_server.hosts: ["https://fleet-server-agent-http.elastic-system.svc:8220"]
    xpack.fleet.packages:
    - name: system
      version: latest
    - name: elastic_agent
      version: latest
    - name: fleet_server
      version: latest
    - name: kubernetes
      version: 1.17.2
    xpack.fleet.agentPolicies:
    - name: Fleet Server on ECK policy
      id: eck-fleet-server
      namespace: default
      monitoring_enabled:
      - logs
      - metrics
      is_default_fleet_server: true
      package_policies:
      - name: fleet_server-1
        id: fleet_server-1
        package:
          name: fleet_server
    - name: Elastic Agent on ECK policy
      id: eck-agent
      namespace: default
      monitoring_enabled:
      - logs
      - metrics
      unenroll_timeout: 900
      is_default: true
      package_policies:
      - package:
          name: system
        name: system-1
      - package:
          name: kubernetes
        name: kubernetes-1
2

I managed to fix this, the github example breaks the authentication for unknown reason

   - package:
          name: system
        name: system-1
      - package:
          name: kubernetes
        name: kubernetes-1

should be

        package_policies:
          - name: system-1
            id: system-1
            package:
              name: system
          - name: kubernetes-1
            id: kubernetes-1
            package:
              name: kubernetes
3

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