update stack versions in recipes/samples and e2e matrix

[kvalliyurnatt]

update stack versions in recipes/samples and e2e matrix post release 9.0.0

[kvalliyurnatt]

buildkite test this -f p=kind -m s=8.18.0,s=9.0.0,s=9.1.0-SNAPSHOT

[kvalliyurnatt]

The e2e test failures seems to be because of a new index being created with replica=1 , so a single node Elasticsearch cluster is not able to reach green status

index                                                              shard prirep state      node                               unassigned.reason
.kibana_locks-000001                                               0     r      UNASSIGNED                                    INDEX_CREATED

I have reached out to the Kibana team about this

[kvalliyurnatt]

fix in progress elastic/kibana#218901

[barkbay]

buildkite test this -f p=kind -m s=8.18.0,s=9.0.0,s=9.1.0-SNAPSHOT

[barkbay]

buildkite test this -f p=kind -m s=8.18.0,s=9.0.0,s=9.1.0-SNAPSHOT

[kvalliyurnatt]

buildkite test this -f p=kind -m s=8.19.0-SNAPSHOT

[prodsecmachine]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[kvalliyurnatt]

in 8.19.0-SNAPSHOT I am seeing the filebeats pods crash with

panic: name processing_time already used

goroutine 1330 [running]:
github.com/elastic/elastic-agent-libs/monitoring.panicErr(...)
	github.com/elastic/elastic-agent-libs@v0.19.1/monitoring/registry.go:257
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).Add(0xc002623240, {0x5586601e40dc?, 0x1?}, {0x558661e94f60, 0xc001be5180}, 0xdc?)
	github.com/elastic/elastic-agent-libs@v0.19.1/monitoring/registry.go:155 +0xca
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).NewRegistry(0xc002623240, {0x5586601e40dc, 0xf}, {0xc0021837d8?, 0x1?, 0x1?})
	github.com/elastic/elastic-agent-libs@v0.19.1/monitoring/registry.go:94 +0x155
github.com/elastic/elastic-agent-libs/monitoring/adapter.NewGoMetrics(0xc002183820?, {0x5586601e40dc?, 0xa?}, {0xc002183920, 0x1, 0x1})
	github.com/elastic/elastic-agent-libs@v0.19.1/monitoring/adapter/go-metrics.go:70 +0x45
github.com/elastic/beats/v7/filebeat/input/filestream/internal/input-logfile.NewMetrics(0xc002623240)
	github.com/elastic/beats/v7/filebeat/input/filestream/internal/input-logfile/metrics.go:72 +0x425
github.com/elastic/beats/v7/filebeat/input/filestream/internal/input-logfile.(*managedInput).Run(_, {0xc002569670, {0xc0020507e0, 0x83}, {0xc0020507e0, 0x83}, {0x5586601cb50d, 0xa}, {{0x5586601c3537, 0x8}, ...}, ...}, ...)
	github.com/elastic/beats/v7/filebeat/input/filestream/internal/input-logfile/input.go:67 +0x1ae
github.com/elastic/beats/v7/filebeat/input/v2/compat.(*runner).Start.func1()
	github.com/elastic/beats/v7/filebeat/input/v2/compat/compat.go:164 +0x523
created by github.com/elastic/beats/v7/filebeat/input/v2/compat.(*runner).Start in goroutine 181
	github.com/elastic/beats/v7/filebeat/input/v2/compat/compat.go:135 +0xb9
panic: name processing_time already used

[kvalliyurnatt]

buildkite test this -f p=kind -m s=8.19.0-SNAPSHOT

[kvalliyurnatt]

beats issue created
elastic/beats#44230

[kvalliyurnatt]

The beats team have identified the root cause and should have a fix for this soon.

[kvalliyurnatt]

fix for the beats issue: https://github.com/elastic/beats/pull/44244/files

once merged I will rerun the tests to verify and then this PR should be ready to be merged

[kvalliyurnatt]

buildkite test this -f p=kind -m s=8.19.0-SNAPSHOT