Skip to content

Fix Kops command to export k8s cluster config #310

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.

Sign up for GitHub

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

Merged
osterman merged 1 commit into from
Dec 13, 2018
Merged

Fix Kops command to export k8s cluster config #310

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/faq/running-kubectl-fails-connection-refused.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,11 @@ The connection to the server localhost:8080 was refused - did you specify the ri

This is most likely caused by not setting the `kubectl` context to use the kops cluster.

To fix this, run `kubectl export kubecfg --name us-west-2.staging.cloudposse.org` (replace our kops cluster name with yours or use the `$KOPS_CLUSTER_NAME` variable, if set). =)
To fix this, run `kops export kubecfg` (this assumes the`$KOPS_CLUSTER_NAME` variable is already set to the cluster name)

e.g.
```
kubectl export kubecfg --name $KOPS_CLUSTER_NAME
kops export kubecfg
```

This will export the `kubecfg` to `/dev/shm`, temporary flash memory storage that should get erased when the container exits.
Expand Down
4 changes: 2 additions & 2 deletions content/secrets-management/kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,9 +17,9 @@ Whether invoking `helm` directly or via `helmfile` all secrets should be passed

## Kubernetes API Credentials

The kubernetes TLS keys are stored by `kops` in a private, encrypted S3 bucket. When using the geodesic shell, you'll need to export these credentials in order to access the kubernetes cluster using `kubectl` or `helm`.
The kubernetes TLS keys are stored by `kops` in a private, encrypted S3 bucket. When using the geodesic shell, you'll need to export these credentials in order to access the kubernetes cluster using `kops` or `helm`.

This is done by running `kubectl export kubecfg $KOPS_CLUSTER_NAME`
This is done by running `kops export kubecfg`

## SSH Access

Expand Down