[Fleet] Accept socks5 proxy url

[nchaulet]

Summary

Resolve #173349
Resolve #158659

Access socks5 proxy url

UI Changes

Todo

• test e2e that agent/fleet server accept it

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[juliaElastic]

LGTM

[nchaulet]

@elasticmachine merge upstream

[jlind23]

@nchaulet I guess this will also resolve: #158659 right?

[nchaulet]

@nchaulet I guess this will also resolve: #158659 right?

Yes it will too, seems it's a duplicate issue

[nchaulet]

tested e2e with agents and mitmproxy in mode socks5 works well

How to test?

Run mitmproxy in socks5 mode

mitmproxy --mode socks5 --ssl-insecure

Set up a proxy in Fleet with the following url socks5://127.0.0.1:1080 and using the mitmproxy CA (by default ~/.mitmproxy/mitmproxy-ca-cert.pem) and add it to your default output

Then enroll an agent.

[nchaulet]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 6a93374
• Cloud Deployment

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
fleet	1.2MB	1.2MB	-39.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
fleet	158.0KB	158.1KB	+84.0B

History

• 💔 Build #186091 failed 3825bf8
• 💔 Build #186048 failed e7b60ec

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @nchaulet