diff --git a/Documentation/deployment-and-configuration.md b/Documentation/deployment-and-configuration.md index f6fd2267a..1305e3c85 100644 --- a/Documentation/deployment-and-configuration.md +++ b/Documentation/deployment-and-configuration.md @@ -54,7 +54,7 @@ ListenStream=127.0.0.1:49153 After you've written the file, call `systemctl daemon-reload` to load the new drop-in, followed by `systemctl stop fleet.service; systemctl restart fleet.socket; systemctl start fleet.service`. Once the socket is running, the fleet API will be available at `http://${ListenStream}/fleet/v1`, where `${ListenStream}` is the value of the `ListenStream` option used in your socket file. -This endpoint is accessible directly using tools such as curl and wget, or you can use fleetctl like so: `fleetctl --driver API --endpoint http://${ListenStream} `. +This endpoint is accessible directly using tools such as curl and wget, or you can use fleetctl like so: `fleetctl --endpoint http://${ListenStream} `. For more information, see the [official API documentation][api-doc]. [api-doc]: https://github.com/coreos/fleet/blob/master/Documentation/api-v1.md diff --git a/Documentation/using-the-client.md b/Documentation/using-the-client.md index 355738027..31e1b0cb1 100644 --- a/Documentation/using-the-client.md +++ b/Documentation/using-the-client.md @@ -7,9 +7,9 @@ fleetctl are analogous to those of systemd's CLI, `systemctl`. The `fleetctl` binary is included in all CoreOS distributions, so it is as simple as SSH'ing in to your CoreOS machine and executing `fleetctl`. -### Custom etcd Endpoint +### Custom API Endpoint -fleetctl currently requires direct communication with the etcd cluster that your fleet machines are configured to use. Use the `--endpoint` flag to override the default of `http://127.0.0.1:2379,http://127.0.0.1:4001`: +fleetctl communicates directly with an HTTP API hosted by the fleet cluster. Use the `--endpoint` flag to override the default of `unix:///var/run/fleet.sock`: fleetctl --endpoint http:// list-units @@ -17,8 +17,6 @@ Alternatively, `--endpoint` can be provided through the `FLEETCTL_ENDPOINT` envi FLEETCTL_ENDPOINT=http:// fleetctl list-units -In future, fleetctl will communicate exclusively with a fleet API endpoint, and will no longer require direct access to etcd. - ### From an External Host If you prefer to execute fleetctl from an external host (i.e. your laptop), the `--tunnel` flag can be used to tunnel communication with your fleet cluster over SSH: