seawolf / turbulence Goto Github PK

View Code? Open in Web Editor NEW

0.0 1.0 0.0 231 KB

Tools to help you connect to Google Cloud pods

Home Page: https://github.com/seawolf/turbulence

Ruby 97.88% Makefile 0.74% Dockerfile 1.38%

turbulence's Introduction

Turbulence

Tools to help you connect to Google Cloud pods.

Rationale

You can point you web browser to https://console.cloud.google.com and click your way to your cloud-deployed servers. You've probably done that before you've contrived the arguably particular commands (providing you installed Python, the Google Cloud SDK and kubectl on your own computer).

If you wanted something simpler than that, just something to get you to the command prompt you're otherwise used to, then this may help.

Usage

Prerequisites

Docker & Docker Compose

Invocation

make

This will:

download and install the Google Cloud SDK into a Docker container, so you need not install it
build the application container, so you don't need Ruby or a local installation
authenticate with Google Cloud, so you can access your GCloud stuff
show your GCloud projects, so you can pick the one you want
show the K8S clusters in that project, so you can pick the one you want
show the K8S namespaces in that cluster, so you can pick the one you want
show the K8S pods in that cluster, so you can pick the one you want
show the K8S containers in that pod, so you can pick the one you want
connect to your container, using bash, so you can do what you wanted to do.

Information entered at each stage will be stored for the next time, up to the pods, though you can start afresh too.

Architecture

Clean-Up

make clean

This will:

stop any currently-running instances
remove the instances
remove cached data, e.g. Google auth tokens, last project used

Changes to the Google APIs may require the Google SDK image to be updated. This can be achieved by:

make vacuum

This will:

all steps in make clean
remove the Google SDK image.

The make command will then download the latest Google SDK image.

turbulence's People

Contributors

Watchers

turbulence's Issues

"Google Cloud CLI changing headless sign-in to the new security flow"

The authentication with Google Cloud may need updating, according this e-mail received from the Google Cloud CLI team:

Hello Ben,

We are writing to let you know that we’re changing an authentication flow you might be using, in order to enhance security. This change requires you to take action by March 15, 2022, to ensure your app continues to work smoothly.

What do I need to know?

You will be impacted by this update if you are using the Out of band OAuth 2.0 flow for gCloud in an environment that doesn’t have a web browser, or if you are using the --no-launch-browser flag.

You can be potentially exposed to remote phishing attacks when you use another computer’s web browser to log in to your Google account and copy the token credentials from that computer’s web browser to reuse in the gCloud CLI running on another machine.

What do I need to do?

To continue using the Out of band OAuth 2.0 flow, you must install gCloud CLI on the local computer (i.e., the one that has a web browser) to generate the credential token for use on the remote Gcloud machine that has no web browser.

Replace your flags ASAP for your own protection by applying any of the actions described in the table below before April 26, 2022 depending on your current flags’ state.

If you’re using the --no-launch-browser flag, replace it with the new --no-browser flag.

If you are not passing any flags when authenticating from a workstation that doesn’t have access to a web browser, add the --no-browser flag

Please consider the following milestones for this change:

Starting with version 377.00 (scheduled for release on March 15, 2022), the new flow will become the default one if your workstation doesn’t have access to a web browser. However, you will be able to keep using the old flow by explicitly passing the --no-launch-browser flag.

Starting with version 383.00 (scheduled for release on April 26, 2022), support for the old flow will be removed from the gCloud CLI.

In addition, after April 26, 2022, attempts to authenticate using the old flow, including from older versions of the gCloud CLI, will result in an error.

`gke-gcloud-auth-plugin` is required

A message has started to appear when running make:

CRITICAL: ACTION REQUIRED: gke-gcloud-auth-plugin, which is needed for continued use of kubectl, was not found or is not executable. Install gke-gcloud-auth-plugin for use with kubectl by following https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke

`rubocop-rspec` gem installed but not activated

Background

The rubocop-rspec gem is included in the project to provide RSpec-related style guidance:
https://github.com/seawolf/turbulence/blob/main/Gemfile#L13

Problem

The gem is not doing anything, as it is not included in the Rubocop configuration:
https://github.com/seawolf/turbulence/blob/main/.rubocop.yml

Actions Needed

main...rubocop-rspec

include the gem in the Rubocop configuration
customise cops for personal preference
auto-correct the codebase
create a TODO list of all remaining violations
remove any remaining violations one-by-one and address them

seawolf / turbulence Goto Github PK

turbulence's Introduction

Turbulence

Rationale

Usage

Prerequisites

Invocation

Architecture

Clean-Up

turbulence's People

Contributors

Watchers

turbulence's Issues

Background

Problem

Actions Needed

Recommend Projects

Recommend Topics

Recommend Org