i just enroll the fleet-server. here's my config
bin/elastic-agent enroll --url=https://192.168.88.147:8220 \
--fleet-server-es=https://192.168.88.147:9200 \
--fleet-server-service-token=token \
--fleet-server-policy=499b5aa7-d214-5b5d-838b-3cd76469844e \
--certificate-authorities=/usr/share/elasticsearch/ca/ca.crt \
--fleet-server-es-ca= /usr/share/elasticsearch/elastic-stack-ca.pem \
--fleet-server-cert=/usr/share/elasticsearch/fleet-server/fleet-server.crt \
--fleet-server-cert-key=/usr/share/elasticsearch/fleet-server/fleet-server.key
and here's the log
2022-06-14T23:31:21.267+0700 INFO cmd/enroll_cmd.go:571 Spawning Elastic Agent daemon as a subprocess to complete bootstrap process.
2022-06-14T23:31:21.402+0700 INFO application/application.go:67 Detecting execution mode
2022-06-14T23:31:21.402+0700 INFO application/application.go:88 Agent is in Fleet Server bootstrap mode
2022-06-14T23:31:21.524+0700 INFO [api] api/server.go:62 Starting stats endpoint
2022-06-14T23:31:21.524+0700 INFO application/fleet_server_bootstrap.go:130 Agent is starting
2022-06-14T23:31:21.524+0700 INFO [api] api/server.go:64 Metrics endpoint listening on: /var/lib/elastic-agent/data/tmp/elastic-agent.sock (configured: unix:///var/lib/elastic-agent/data/tmp/elastic-agent.sock)
2022-06-14T23:31:21.525+0700 INFO application/fleet_server_bootstrap.go:140 Agent is stopped
2022-06-14T23:31:21.526+0700 INFO stateresolver/stateresolver.go:48 New State ID is GOf8afVg
2022-06-14T23:31:21.527+0700 INFO stateresolver/stateresolver.go:49 Converging state requires execution of 1 step(s)
2022-06-14T23:31:21.557+0700 INFO operation/operator.go:284 operation 'operation-install' skipped for fleet-server.7.17.4
2022-06-14T23:31:21.785+0700 INFO log/reporter.go:40 2022-06-14T23:31:21+07:00 - message: Application: fleet-server--7.17.4[]: State changed to STARTING: Starting - type: 'STATE' - sub_type: 'STARTING'
2022-06-14T23:31:21.785+0700 INFO stateresolver/stateresolver.go:66 Updating internal state
2022-06-14T23:31:22.269+0700 INFO cmd/enroll_cmd.go:776 Fleet Server - Starting
2022-06-14T23:31:23.303+0700 WARN status/reporter.go:236 Elastic Agent status changed to: 'degraded'
2022-06-14T23:31:23.304+0700 INFO log/reporter.go:40 2022-06-14T23:31:23+07:00 - message: Application: fleet-server--7.17.4[]: State changed to DEGRADED: Running on policy with Fleet Server integration: 499b5aa7-d214-5b5d-838b-3cd76469844e; missing config fleet.agent.id (expected during bootstrap process) - type: 'STATE' - sub_type: 'RUNNING'
2022-06-14T23:31:24.271+0700 INFO cmd/enroll_cmd.go:757 Fleet Server - Running on policy with Fleet Server integration: 499b5aa7-d214-5b5d-838b-3cd76469844e; missing config fleet.agent.id (expected during bootstrap process)
2022-06-14T23:31:24.943+0700 INFO cmd/enroll_cmd.go:454 Starting enrollment to URL: https://192.168.88.147:8220/
2022-06-14T23:31:25.670+0700 INFO cmd/enroll_cmd.go:258 Elastic Agent has been enrolled; start Elastic Agent
Successfully enrolled the Elastic Agent.
2022-06-14T23:31:25.670+0700 INFO cmd/run.go:184 Shutting down Elastic Agent and sending last events...
2022-06-14T23:31:25.670+0700 INFO operation/operator.go:216 waiting for installer of pipeline 'default' to finish
2022-06-14T23:31:25.670+0700 INFO process/app.go:176 Signaling application to stop because of shutdown: fleet-server--7.17.4
2022-06-14T23:31:27.171+0700 INFO status/reporter.go:236 Elastic Agent status changed to: 'online'
2022-06-14T23:31:27.171+0700 INFO cmd/run.go:192 Shutting down completed.
2022-06-14T23:31:27.171+0700 INFO [api] api/server.go:66 Stats endpoint (/var/lib/elastic-agent/data/tmp/elastic-agent.sock) finished: accept unix /var/lib/elastic-agent/data/tmp/elastic-agent.sock: use of closed network connection
2022-06-14T23:31:27.171+0700 INFO log/reporter.go:40 2022-06-14T23:31:27+07:00 - message: Application: fleet-server--7.17.4[]: State changed to STOPPED: Stopped - type: 'STATE' - sub_type: 'STOPPED'
but why it still Waiting for Fleet Server to connect... in my kibana?