Weave Cloud Deploy consists of a daemon which runs in your cluster, the web GUI, and optionally a command-line interface
fluxctl. Once you have the daemon running, you can access it through
Deploy assumes that you have set up your deployment YAML for your Kubernetes services. See Setting up Your Manifests
Note: You can just use the Weave Cloud GUI and it is not necessary to use the command-line utility, unless you prefer working that way.
The following topics are discussed:
1. Find and copy the URL to the binary that you want to install from the Flux releases page.
sudo curl -L https://github.com/weaveworks/flux/releases/[release]/[binary-file] -o /usr/local/bin/fluxctl sudo chmod a+x /usr/local/bin/fluxctl
[release]/[binary-file] is the path to the release number and binary file on the Flux releases page.
You may have other methods beside
curl of downloading the binaries to your desktop.
Supported binaries include:
- Darwin AMD64 (MacOS)
- Linux AMD64
2. Next, configure access to your Weave Cloud instance with:
If you log out of your shell, you must re-run
export WEAVE_CLOUD_TOKEN=<weave-cloud-token> to re-establish your environment.
3. Give the daemon access to your git repository.
Note: If you’ve already pushed the ssh key to your repo through the GUI, then this step is not necessary.
If your repository is hosted at Github, the Flux daemon running in your cluster will need a Deploy Key to be able to read and write to it.
You can get the current public key by running:
You can generate a new key by running:
fluxctl identity --regenerate
To manually set your public key up for your repo:
1. Go to the
<YOUR_GITHUB_USERNAME>/<your code> repo on github, and click Settings from the top of the repo.
2. Click on Deploy Keys from the left-hand menu.
3. Click Add a Key, and then paste in your public key requested above (using
Allow Read/Write access box so that Weave Cloud deploy has full access to the repo.
To check the keys match, you can compare the fingerprint shown in Github with the output of
fluxctl identity --fingerprint
If you are not using Github, the method of installing the public key will vary. See for example, the GitLab documentation on using SSH keys.