geodesic

• Geodesic PR #587

• See https://github.com/cloudposse/packages/pull/375

• Lots of tool updates

PR #586

If you want to run docker commands from within Geodesic, this update brings Geodesic's support up-to-date with Docker Desktop's evolution. It has been tested on Linux and macOS Catalina and is expected to work on WSL.

• WITH_DOCKER=true geodesic
• apk add docker-cli

Use chamber env instead of chamber -f dotenv (#585)

Includes helm and helmfile support for automatic creation of Kubernetes namespaces

See #579 for details.

In short, if you are not happy with they way aws-vault version 5 (the current version) is working, you can revert to version 4 by adding

apk add -u aws-vault@cloudposse~=4

to your Dockerfile anywhere after

FROM cloudposse/geodesic:0.130.0

Tool/dependency updates (#576)

Tool/dependency updates (#571)

UI support for EKS, SAML auth, and Terraform Workspaces (#566)

Tag running Docker container with APP_NAME when set (#565)

PR #556

• Drop Python 2.x, awsebcli
• Add boto3 1.11.14
• Alpine 3.10.2 -> 3.11.3
• PyYAML 3.13 -> 5.2
• ansible 2.8.5 -> 2.9.4
• awscli 1.16.250 -> 1.17.14
• crudini 0.9 -> 0.9.3
• Jinja 2.10.1 -> 2.11.1
• google/cloud-sdk 276.0.0 -> 278.0.0

Users running Docker for Mac 2.2.0.0 or later can set

export GEODESIC_MAC_FORWARD_SOCKET=true

before running Geodesic and now SSH keys added to ssh-agent on the Mac host will be available from inside the Geodesic container. You no longer need to mount and unlock keys on every invocation of Geodesic.

The Docker server socket is also forwarded if $WITH_DOCKER == "true"

Thanks to @tamsky #534

#552 Allow configuration of helm binary for destroy-namespace by setting HELM_BINARY env var

Note

Support for aws-vault version 4 was removed in this release, but restored in version 0.130.0. See #579.

Breaking Change

Update to helm 3, aws-vault 5 (#546)

helm version 2 is available as helm2 or you can set it as helm using

update-alternatives --set helm /usr/share/helm/2/bin/helm2

helm version 3 is available as helm3 and by default as helm

You can tell helmfile which helm version to use via the -b flag

helmfile -b helm2 ...

If you were installing helm yourself, using something like

apk add helm@cloudposse==2.14.3-r0

then that version of helm will be used as helm. It will share plugins with helm2 or helm3 depending on which version it is.

Update package manager indexes to bring in updated packages