Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option#20713
Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option#20713ycombinator merged 3 commits intoelastic:masterfrom ycombinator:agent-insecure-env-var
Conversation
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
jenkins, test this |
|
CI failures seem unrelated to this PR as the failures are also seen on |
…ecure CLI option (#20713) (#20740) * Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option (#20713) * Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option * Adding CHANGELOG entry * Adding issue to CHANGELOG entry # Conflicts: # x-pack/elastic-agent/CHANGELOG.asciidoc * Fixing up CHANGELOG
…astic#20713) * Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option * Adding CHANGELOG entry * Adding issue to CHANGELOG entry
…ecure CLI option (elastic#20713) (elastic#20740) * Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option (elastic#20713) * Add FLEET_ENROLL_INSECURE env var to expose --insecure CLI option * Adding CHANGELOG entry * Adding issue to CHANGELOG entry # Conflicts: # x-pack/elastic-agent/CHANGELOG.asciidoc * Fixing up CHANGELOG
What does this PR do?
This PR adds a new environment variable to the
elastic-agentDocker entrypoint file:FLEET_ENROLL_INSECURE. It corresponds to the--insecureflag accepted by theelastic-agentCLI when enrolling with Fleet.Why is it important?
In development and testing environments, it is convenient to spin up Kibana without TLS. To allow Elastic Agent to enroll with Fleet running in such a Kibana instance, it is necessary to use the
--insecureflag during enrollment.Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues