[automation] update elastic stack version for testing 8.2.0-5d69c4c3

[apmmachine]

What

Bump stack version with the latest one.

Further details

[start_time:Mon, 7 Feb 2022 16:39:23 GMT, release_branch:master, prefix:, end_time:Mon, 7 Feb 2022 21:34:27 GMT, manifest_version:2.0.0, version:8.2.0-SNAPSHOT, branch:master, build_id:8.2.0-5d69c4c3, build_duration_seconds:17704]

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-09T05:16:46.018+0000

• Duration: 61 min 32 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5626
Skipped	19
Total	5645

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /hey-apm : Run the hey-apm benchmark.

• /package : Generate and publish the docker images.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[ph]

@axw using this patch it correctly start the Elastic Agent, see elastic/fleet-server#1129 (comment) for more details, this might need adjustment.

diff --git a/docker-compose.yml b/docker-compose.yml
index 832cb580d..113d3b0d2 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -56,12 +56,12 @@ services:
       XPACK_SECURITY_ENCRYPTIONKEY: "fhjskloppd678ehkdfdlliverpoolfcr"
       XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY: "fhjskloppd678ehkdfdlliverpoolfcr"
       XPACK_FLEET_AGENTS_ELASTICSEARCH_HOST: "http://elasticsearch:9200"
-      XPACK_FLEET_AGENTS_TLSCHECKDISABLED: "true"
       XPACK_FLEET_REGISTRYURL: "http://package-registry:8080"
     depends_on:
       elasticsearch: { condition: service_healthy }
       package-registry: { condition: service_healthy }
-
+    volumes:
+      - "./kbn.yml:/usr/share/kibana/config/kibana.yml"
   fleet-server:
     image: docker.elastic.co/beats/elastic-agent:8.2.0-5d69c4c3-SNAPSHOT
     ports:
diff --git a/kbn.yml b/kbn.yml
new file mode 100644
index 000000000..0fe18acfd
--- /dev/null
+++ b/kbn.yml
@@ -0,0 +1,44 @@
+server.name: kibana
+server.host: "0.0.0.0"
+
+elasticsearch.hosts: [ "http://elasticsearch:9200" ]
+
+monitoring.ui.container.elasticsearch.enabled: true
+
+xpack.fleet.registryUrl: "http://package-registry:8080"
+xpack.fleet.agents.enabled: true
+xpack.fleet.agents.elasticsearch.hosts: ["http://elasticsearch:9200"]
+xpack.fleet.agents.fleet_server.hosts: ["http://fleet-server:8220"]
+
+xpack.encryptedSavedObjects.encryptionKey: "12345678901234567890123456789012"xpack.fleet.packages:
+  - name: system
+    version: latest
+  - name: elastic_agent
+    version: latest
+  - name: fleet_server
+    version: latest
+
+xpack.fleet.agentPolicies:
+  - name: Elastic-Agent (elastic-package)
+    id: elastic-agent-managed-ep
+    is_default: true
+    is_managed: false
+    namespace: default
+    monitoring_enabled:
+      - logs
+      - metrics
+    package_policies:
+      - name: system-1
+        id: default-system
+        package:
+          name: system
+  - name: Fleet Server (elastic-package)
+    id: fleet-server-managed-ep
+    is_default_fleet_server: true
+    is_managed: false
+    namespace: default
+    package_policies:
+      - name: fleet_server-1
+        id: default-fleet-server
+        package:
+          name: fleet_server

 ❯ docker-compose up -d                                                                                  [15:43:57]
Docker Compose is now in the Docker CLI, try `docker compose up`

Creating network "apm-server_default" with the default driver
Creating apm-server_package-registry_1 ... done
Creating apm-server_elasticsearch_1    ... done
Creating apm-server_kibana_1           ... done
Creating apm-server_fleet-server_1     ... done
Creating apm-server_proxy_dep_1        ... done
>>> elapsed time 2m29s       

[axw]

Thanks for digging into it @ph. I wasn't aware of the removal of the default Fleet Server policy.

[axw]

/test

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-09T06:17:56.738+0000

• Duration: 60 min 20 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5626
Skipped	19
Total	5645

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /hey-apm : Run the hey-apm benchmark.

• /package : Generate and publish the docker images.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[simitt]

@ph thanks for the fix!
Isn't this a breaking change to not have the Fleet Server policy installed anymore by default?

[mtojek]

FYI @juliaElastic @joshdover It looks like APM is another team depending on this change.

[juliaElastic]

@mtojek thanks for raising, we weren't aware of this dependency. Is it used for testing?
@simitt this change impacts new on-prem deployments, existing ones and Cloud are still going to have default Fleet Server policy.