Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-21 16:08:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 100
fleet/docs/02-Deploying/01-Installation.md

77 lines
4 KiB
Markdown
Raw Normal View History

Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
# Installation
Update documentation about TLS configuration (#656)
2021-04-19 18:58:44 +00:00
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
- [Installing the Fleet binary](#installing-the-fleet-binary)
- [Docker container](#docker-container)
- [Raw binaries](#raw-binaries)
Update documentation about TLS configuration (#656)
2021-04-19 18:58:44 +00:00
- [TLS configuration](#tls-configuration)
- [TLS certificate considerations](#tls-certificate-considerations)
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
- [Infrastructure dependencies](#infrastructure-dependencies)
Update documentation about TLS configuration (#656)
2021-04-19 18:58:44 +00:00
- [MySQL](#mysql)
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
- [Redis](#redis)
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
The Fleet application is distributed as a single static binary. This binary serves:
- The Fleet web interface
- The Fleet application API endpoints
- The osquery TLS server API endpoints
fix broken links by adding missing 0 (#2187) * fix broken links by adding missing 0 * fix broken links take 2 gather links missed in first pass
2021-09-22 16:28:25 +00:00
All of these are served via a built-in HTTP server, so there is no need for complex web server configurations. Once you've installed the `fleet` binary and it's infrastructure dependencies as illustrated below, refer to the [Configuration](./02-Configuration.md) documentation for information on how to use and configure the Fleet application.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
## Installing the Fleet binary
Update documentation about TLS configuration (#656)
2021-04-19 18:58:44 +00:00
There are multiple options available for installing the Fleet binary.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
### Docker container
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Pull the latest Fleet docker image:
```
Changes to additional links for transition to fleetdm (#21)
2020-11-05 05:48:39 +00:00
docker pull fleetdm/fleet
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
```
fix broken links by adding missing 0 (#2187) * fix broken links by adding missing 0 * fix broken links take 2 gather links missed in first pass
2021-09-22 16:28:25 +00:00
For more information on using Fleet, refer to the [Configuration](./02-Configuration.md) documentation.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
### Raw binaries
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Update 1-Installation.md
2021-07-01 20:57:35 +00:00
Download the latest raw Fleet binaries with `curl` or from the ["Releases" page on GitHub](https://github.com/fleetdm/fleet/releases).
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Unzip the binaries for your platform:
```
# For a Darwin compatible binary
Update docs and Makefile to use Github releases for binaries (#2055)
2019-06-04 17:42:41 +00:00
unzip fleet.zip 'darwin/*' -d fleet
Updating docs to reference new binary and package (#1557)
2017-10-06 01:33:41 +00:00
./fleet/darwin/fleet_darwin_amd64 --help
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
# For a Linux compatible binary
Update docs and Makefile to use Github releases for binaries (#2055)
2019-06-04 17:42:41 +00:00
unzip fleet.zip 'linux/*' -d fleet
Updating docs to reference new binary and package (#1557)
2017-10-06 01:33:41 +00:00
./fleet/linux/fleet_linux_amd64 --help
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
```
fix broken links by adding missing 0 (#2187) * fix broken links by adding missing 0 * fix broken links take 2 gather links missed in first pass
2021-09-22 16:28:25 +00:00
For more information on using Fleet, refer to the [Configuration](./02-Configuration.md) documentation.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Update documentation about TLS configuration (#656)
2021-04-19 18:58:44 +00:00
## TLS configuration
In order for osqueryd clients to connect, the connection to Fleet must use TLS. The TLS connection may be terminated by Fleet itself, or by a proxy serving traffic to Fleet.
### TLS certificate considerations
- The CNAME or one of the Subject Alternate Names (SANs) on the certificate must match the hostname that osquery clients use to connect to the server/proxy.
- If self-signed certificates are used, the full certificate chain must be provided to osquery via the `--tls_server_certs` flag.
- If Fleet terminates TLS, consider using an ECDSA (rather than RSA) certificate, as RSA certificates have been associated with [performance problems in Fleet due to Go's standard library TLS implementation](https://github.com/fleetdm/fleet/issues/655).
## Infrastructure dependencies
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Updating docs to reference new binary and package (#1557)
2017-10-06 01:33:41 +00:00
Fleet currently has two infrastructure dependencies in addition to the `fleet` web server itself. Those dependencies are MySQL and Redis.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
### MySQL
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
fix broken links by adding missing 0 (#2187) * fix broken links by adding missing 0 * fix broken links take 2 gather links missed in first pass
2021-09-22 16:28:25 +00:00
Fleet uses MySQL extensively as its main database. Many cloud providers (such as [AWS](https://aws.amazon.com/rds/mysql/) and [GCP](https://cloud.google.com/sql/)) host reliable MySQL services which you may consider for this purpose. A well supported MySQL [Docker container](https://hub.docker.com/_/mysql/) also exists if you would rather run MySQL in a container. For more information on how to configure the `fleet` binary to use the correct MySQL instance, see the [Configuration](./02-Configuration.md) document.
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
Add MySQl version information to infra docs (#1919)
2018-09-11 17:56:14 +00:00
Fleet requires at least MySQL version 5.7.
Add automatic host expiration capability (#2117) When configured, this feature will delete hosts that have not checked in after the specified number of days. Closes #1860.
2019-10-16 23:35:17 +00:00
For host expiry configuration, the [event scheduler](https://dev.mysql.com/doc/refman/5.7/en/events-overview.html) must be enabled. This can be enabled via the command line, configuration file, or a user with the required privileges.
Part 1 of documentation restructure. Deployment section. (#147) This PR includes the Deployment section of the documentation restructure #144. - Changes include the addition of 3 overarching folders/sections named Deployment, Using fleet, and Contribution guide. Each folder includes new files for the subsections. - Move the copy from the appropriate files into the new files in the Deployment folder. Removed old files. A detailed outline of the exact old files can be found in the linked issue above. - Add navigation to the top of each file via links to anchors in the markdown. The naming convention for each folder and file is up for discussion. I chose to use number prefixes (1, 2, 3) to order the folders and files. This way we have control over the order when viewing on GitHub.
2020-12-24 22:00:22 +00:00
### Redis
Rename Kolide to Fleet in the docs (#1554)
2017-09-21 22:51:26 +00:00
fix broken links by adding missing 0 (#2187) * fix broken links by adding missing 0 * fix broken links take 2 gather links missed in first pass
2021-09-22 16:28:25 +00:00
Fleet uses Redis to ingest and queue the results of distributed queries, cache data, etc. Many cloud providers (such as [AWS](https://aws.amazon.com/elasticache/) and [GCP](https://console.cloud.google.com/launcher/details/click-to-deploy-images/redis)) host reliable Redis services which you may consider for this purpose. A well supported Redis [Docker container](https://hub.docker.com/_/redis/) also exists if you would rather run Redis in a container. For more information on how to configure the `fleet` binary to use the correct Redis instance, see the [Configuration](./02-Configuration.md) document.
Reference in a new issue Copy permalink