fleet/test/upgrade
Lucas Manuel Rodriguez 1f97514200
Only set public IPs on host.public_ip and add docs (#9900)
#9857

The "Public IP address" field is sometimes set to a "Private IP" on the
following types of Fleet deployments:
- Local deployments.
- Deployments where Fleet is on a private network.
- Deployments where an agent connects to Fleet not via the public
internet.

This PR will prevent a private IP to be set on the `host.public_ip`
field.
And this PR also adds documentation on how Fleet deduces the public IPs
of the devices so that a user can make the changes to fix this.

- [X] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- ~[ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)~
- ~[ ] Documented any permissions changes~
- ~[ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)~
- ~[ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.~
- ~[ ] Added/updated tests~
- [X] Manual QA for all new/changed functionality
  - ~For Orbit and Fleet Desktop changes:~
- ~[ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.~
- ~[ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).~
2023-02-17 13:00:56 -03:00
..
nginx add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
docker-compose.yaml Only set public IPs on host.public_ip and add docs (#9900) 2023-02-17 13:00:56 -03:00
fleet_test.go add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
fleet.crt add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
fleet.key add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
generate_cert.sh add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
osquery.flags add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00
README.md Fleet 4.18.0 changelog (#6951) 2022-08-01 13:39:13 -07:00
upgrade_test.go add upgrade tests (#6596) 2022-07-19 15:11:51 -06:00

Upgrade Tests

The tests located in test/upgrade are intended to test fleet upgrades with online migrations as proposed in #6376. To run the tests, you need to specify the from and to versions. For example

$ FLEET_VERSION_A=v4.16.0 FLEET_VERSION_B=v4.18.0 go test ./test/upgrade

Ensure that Docker is installed with Compose V2. To check if you have the correct version, run the following command

$ docker compose version
Docker Compose version v2.6.0