Skip to main content
100%

Obtain GKE Basic Auth Credentials and use them

✓ Published0🌍 Public
Aankuagar
Last edited Jul 23, 2019
Created on Oct 31, 2020

This example demonstrates how to obtain GKE basic authentication credentials from a cluster’s metadata and use them to construct a kubeconfig file for subsequent kubectl commands. The script fetches the cluster metadata via `gcloud container clusters describe`, then uses `jq` to extract the CA certificate, endpoint, and password. It writes a kubeconfig file with the admin username and password, then runs `kubectl get clusterroles` against that config to verify access. The code relies on the Google Cloud CLI and `jq` for JSON parsing.

AI-generated description

Similar vizzes

Loading thumbnail…

Kubernetes cheat sheet

This cheat sheet shows operational commands for debugging a Kubernetes cluster, organized by component such as K8s cluster, etcd, networking, and worker nodes. It lists shell commands and kubectl invocations for retrieving cluster info, viewing logs, and inspecting DNS or node status, with links to official documentation. The plain-text markdown file uses code blocks and headings to group commands by topic, relying on Kubernetes APIs like `kubectl get`, `kubectl logs`, and `journalctl`. It does not include charts or interactive elements; the rendering is static text.

Aankuagar
59% match
Loading thumbnail…

Gist 682c0ed12e0006118fb5287146247844

This example shows a Bash script that automates the migration of Kubernetes deployment configurations and Argo CD application manifests for a service across multiple environments. It creates new cluster directories by copying existing ones, generates an ingress DNS patch file, and updates the kustomization.yaml with the new patch reference. The script also writes a kustomization file for the Argo application that points to the newly created deployment path. It uses the `gsed` command for in-place text replacement and `echo` to generate YAML content, operating on files within a specified current working directory.

Aamazingandyyy
55% match
Loading thumbnail…

Copy kubernetes secrets between namespaces

This example demonstrates a shell one-liner that copies Kubernetes secrets from one namespace to another. It uses `kubectl get secrets` with JSON output to retrieve the source secrets, then pipes the result through `jq` to rewrite the `metadata.namespace` field to the target namespace. The transformed JSON is applied directly with `kubectl apply -f -`. The visualization highlights the command pipeline’s data flow, relying on the Kubernetes CLI and jq for JSON manipulation, with no additional charting or rendering libraries involved.

TThanad
54% match
Loading thumbnail…

k8s

This visualization is a reference cheat sheet for command-line workflows, primarily centered on Kubernetes cluster management, SSH key handling, and Docker operations. It presents plain-text code snippets and terminal output showing commands like `kubectl config get-contexts`, `ssh-add -l`, and `docker build`, along with the expected results. The examples cover additional utilities such as `git diff`, `rsync`, `ffmpeg` encoding, and PDF conversion with `convert` and `montage`. The data shown is static text and command outputs, not a graphical rendering, so no visualization libraries are used.

Aabernier
54% match
Loading thumbnail…

Read only cluster role for Lens read only users

This example visualizes a Kubernetes RBAC configuration by defining a `ClusterRole` named `read-only-clusterrole` for Lens read-only users. It shows the explicit mapping of permitted API groups, resources, and HTTP verbs—using `get`, `list`, and `watch`—across a broad set of Kubernetes object types. The YAML file enumerates resources such as pods, deployments, services, and custom endpoints, specifying non-resource URLs like `/metrics`. The code relies on the Kubernetes RBAC API schema to structure permissions, rendering a declarative security policy that restricts access to read-only operations. This illustrates how fine-grained access control is encoded using YAML syntax within a Kubernetes cluster role definition.

TThanad
51% match
Loading thumbnail…

Gist a9811ea9c0293f1b19277f7a6995b236

This example shows a bash script that automates the setup of a Linux scavenger-hunt lab environment. It downloads an SSH deploy key, clones a Git repository from GitLab, initializes submodules, and uses Vagrant to provision the virtual machine. The script concludes by parsing `vagrant ssh-config` output with `awk` and `sed` to display the student’s SSH connection details, including hostname and port.

PPeleke
50% match
Loading thumbnail…

Gist abca832946db64106b24e4927e369a11

This example shows a Bash script that automates the setup of a Linux scavenger-hunt lab environment, from downloading a deploy key to provisioning a virtual machine. The script uses `curl` to fetch an SSH private key, `git clone` and `git submodule update --init --recursive` to retrieve the lab definitions, and `vagrant up` to launch the machine. It then parses `vagrant ssh-config` output with `grep`, `awk`, and `sed` to extract the hostname and port, printing SSH connection instructions for the student user.

PPeleke
49% match
Loading thumbnail…

Gist 0711211684d6b9f38dc69fe06a29d844

This example shows a shell script that automates the setup of a Linux scavenger hunt lab environment by downloading a deploy key, cloning a GitLab repository, and running Vagrant to provision the machine. The script uses `curl` to fetch an SSH key, `git clone` with submodules to pull the lab definitions, and `vagrant up` to launch the virtual machine. It then extracts the SSH hostname and port from `vagrant ssh-config` using `grep` and `awk`, printing connection instructions for the student user.

PPeleke
49% match