Download Latest Version infra_0.21.0_darwin_x86_64.zip (17.1 MB)
Email in envelope

Get an email when there's a new version of Infra

Home / v0.18.0
Name Modified Size InfoDownloads / Week
Parent folder
infra-0.18.0-aarch64.rpm 2022-11-22 16.8 MB
0
infra-0.18.0-x86_64.rpm 2022-11-22 18.7 MB
0
infra_0.18.0_arm64.deb 2022-11-22 16.9 MB
0
infra_0.18.0_amd64.deb 2022-11-22 18.8 MB
0
infra_0.18.0_windows_x86_64.zip 2022-11-22 18.0 MB
0
infra-checksums.txt 2022-11-22 841 Bytes
0
infra_0.18.0_darwin_arm64.zip 2022-11-22 18.0 MB
0
infra_0.18.0_darwin_x86_64.zip 2022-11-22 18.8 MB
0
infra_0.18.0_linux_arm64.zip 2022-11-22 16.2 MB
0
infra_0.18.0_linux_x86_64.zip 2022-11-22 17.9 MB
0
README.md 2022-11-22 10.2 kB
0
v0.18.0 source code.tar.gz 2022-11-22 20.3 MB
0
v0.18.0 source code.zip 2022-11-22 20.6 MB
0
Totals: 13 Items   200.8 MB 0

image of a golden key on a hand with crystallized silicon in the background to represent Infra version 0.18

Infra Access Keys

screenshot of infra dashboard Infra's access keys can now be generated in the dashboard. This unlocks many use cases. Some examples include:

  • Dynamically changing/revoking permissions for users and groups
  • CI/CD infrastructure access (i.e. GitHub Actions)
  • Other actions that can be performed via Infra API

Caveats:

Currently, access keys share the same permissions as the user who created it. This is not very ideal for users who want to have scoped keys that have dedicated use cases. This problem will be addressed in the future.

For now, it is advisable to create another user, assign only limited permissions for that user, and login as that user to generate an access key for usage. Once this is created, the administrator account can be used to scope the permissions of that user (or multiple users).

Improved Kubeconfig support for multiple namespaces

For Kubernetes clusters where a user/group has access to multiple individual namespaces, only one kubeconfig context will be created for a single cluster. Previously, if a user had access to multiple namespaces within a cluster, the user will receive a context for each individual namespace.

CLI quality of life improvements

  • Change access keys to make their names unique to a specific user, instead of for an entire org
  • Make infra keys list default to the current user
  • Add an --all flag to infra keys list for admins which can list all access keys in the org
  • Make infra keys add not require a user name
  • Add a --user= argument to infra keys add to be consistent with infra keys list
  • Add a --connector flag to infra keys add to create the key for a connector
  • Make infra keys remove to be specific to the current user
  • Add a --user= argument similar to infra keys list and infra keys add
  • Changed the API to call DELETE /api/access-keys/:id instead of DELETE /api/access-keys
  • Added LastUsed field to the API and updated infra keys list to show the last time a specific key was used

Full Changelog

Source: README.md, updated 2022-11-22