Antoine Cotten

@AgingOrange the original author emerged back from nowhere just to literally delete the entire Git history, then went dormant again. See https://github.com/base16-project/home/issues/51 for some context about where the reboot of...

@koosvriezen thanks for reporting! The patch looks reasonable ✅

@ublsoftware unfortunately not at that stage. The PKI is generated locally, in memory, during the cluster creation. It is not persisted between runs so in order to add nodes one...

@SamTV12345 I can't think about a reason for agents not to work properly with this stack, unless they are trying to communicate over a port that isn't exposed on the...

@SamTV12345 looking into this today.

@SamTV12345 I'm observing the same behavior. Agents register OK but don't send any data, for reasons I can't comprehend. I see no error whatsoever in the logs. I've been following...

Actually, I found something in the agent's logs in `/usr/share/elastic-agent/state/data/logs/default/...`: ```json { "log.level": "error", "@timestamp": "2022-08-11T21:21:25.836Z", "log.logger": "publisher_pipeline_output", "log.origin": { "file.name": "pipeline/client_worker.go", "file.line": 150 }, "message": "Failed to connect to...

Yes while playing with Fleet yesterday (first time to be honest with you) I realized it could be useful to have a containerized Fleet "extension" with setup instructions in the...

This feature request is now being tracked in #749.

I think the easiest way would be 1. Initialize the keystore using Docker, without Compose: ```console $ docker run --rm -v $(pwd)/elasticsearch/config/:/usr/share/elasticsearch/config/ docker.elastic.co/elasticsearch/elasticsearch:7.11.1 elasticsearch-keystore create ``` 1. Mount the pre-created...