[elastic-agent] Use fleet.url for container cmd #25026
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When running the elastic-agent container command with
fleet-server.enable:true
and providing--url
,--fleet-server-cert
and--fleet-server-cert-key
, the container returns a setup error, claiming thaturl
is not set.This PR ensures that the URL is also set for fleet server setup.
Previous related: #24904
Why is it important?
This is important as otherwise no certificate and cert-key could ever be configured for the Fleet Server. When only Fleet Server and Elastic-Agent communicate with each other, certificates are created on-the-fly and communication is secured. But one also needs to be able to use a secure connection and certificates e.g. from a proxy to the Fleet Server.