Add support to define expose ports for independent agents

[mrodm]

Part of #787
Relates #1262 #1355

This PR allows users to define which ports should be exposed from the Elastic Agent container.ç
This definition should be added to the system configuration file. Example:

agent:
  ports:
    - "127.0.0.1:3000:3000"

This example is based on agents using docker as a runtime https://docs.docker.com/compose/compose-file/compose-file-v2/#ports

[jsoriano]

👍

[jsoriano]

Nit. Have you thought about calling this just ports?

Suggested change

	ExposePorts []string `config:"expose_ports"`
	ExposePorts []string `config:"ports"`

[mrodm]

I wanted to emphasize that these ports are the ones to be exposed. But re-thinking that idea, if it used ports as the name in those settings, it looks like is clear that it refers to the ports to be exposed (or forwarded from the host like in VMs).

For instance, docker-compose uses ports: https://docs.docker.com/compose/compose-file/compose-file-v3/#ports
But in Vargrantfile, it is used forwarded_ports: https://developer.hashicorp.com/vagrant/docs/networking/forwarded_ports#defining-a-forwarded-port

I think it could be just "ports".

I'll update the PR

[mrodm]

Updated in 2af3fac

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 2af3fac

History

• 💛 Build #2911 was flaky d9e2124

cc @mrodm