Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

re-flow GKE note in get-started doc #1489

Merged
merged 1 commit into from Nov 5, 2018
Merged
Changes from all commits
Commits
File filter...
Filter file types
Jump to…
Jump to file or symbol
Failed to load files and symbols.

Always

Just for now

the note on GKE somewhat interrupted the flow, re-flow parts of the d…

…oc to make things clearer

Signed-off-by: Daniel Holbach <daniel@weave.works>
  • Loading branch information
dholbach committed Nov 2, 2018
commit 57d81c9fc4ed12ec912031a168a61b791be75f2f
@@ -24,14 +24,27 @@ When using nodes of only 1 cpu (like `n1-standard-1`), an upgrade
may be stuck with not enough CPU resources. This is seen by pods
hanging in PENDING state and with:

```
```sh
$ kubectl describe pod/helloworld-... | tail -3
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 3m (x37 over 13m) default-scheduler 0/2 nodes are available: 2 Insufficient cpu.
```

### A Note on GKE with RBAC enabled

> If working on e.g. GKE with RBAC enabled, you will need to add a clusterrolebinding:
>
> ```sh
> kubectl create clusterrolebinding "cluster-admin-$(whoami)" --clusterrole=cluster-admin --user="$(gcloud config get-value core/account)"
> ```
> to avoid an error along the lines of
>
> `Error from server (Forbidden): error when creating "deploy/flux-account.yaml":
> clusterroles.rbac.authorization.k8s.io "flux" is forbidden: attempt to grant
> extra privileges:`
## Set up Flux

Get Flux:
@@ -55,16 +68,7 @@ In our example we are going to use
want to use that too, be sure to create a fork of it on Github and
add the git URL to the config file above.

If working on e.g. GKE with RBAC enabled, you will need to add a clusterrolebinding:

```sh
kubectl create clusterrolebinding "cluster-admin-$(whoami)" --clusterrole=cluster-admin --user="$(gcloud config get-value core/account)"
```
to avoid an error along the lines of

`Error from server (Forbidden): error when creating "deploy/flux-account.yaml":
clusterroles.rbac.authorization.k8s.io "flux" is forbidden: attempt to grant
extra privileges:`
## Deploying Flux to the cluster

In the next step, deploy Flux to the cluster:

ProTip! Use n and p to navigate between commits in a pull request.
You can’t perform that action at this time.