v0.6.0

[gardener/gardenlogin]

✨ New Features

• [DEVELOPER] gosec was introduced for Static Application Security Testing (SAST). by @petersutter [#158]

📖 Documentation

• [USER] Fix for install doc on linux by @elankath [#148]

v0.5.1

[gardener/gardenlogin]

🏃 Others

• [USER] The log entry when falling back to shoots/viewerkubeconfig is now only shown when using verbosity level 4 (--v=4) or higher by @petersutter [#83]

v0.5.0

[gardener/gardenlogin]

✨ New Features

• [USER] gardenlogin is now also available for linux/arm64 by @petersutter [#72]
• [USER] get-client-certificate: Viewer credentials can now be requested using the flag --access-level=viewer. The default access-level option is auto, which first attempts to fetch admin-level credentials and falls back to viewer-level credentials if the former is unsuccessful. by @petersutter [#78]

v0.4.0

[gardenlogin]

⚠️ Breaking Changes

• [USER] The deprecated config properties (since v0.2.0, #20) are not supported anymore. If not already done update your config file: (gardener/gardenlogin#46, @petersutter)
  • gardenClusters was renamed to gardens
  • clusterIdentity was renamed to identity
• [DEVELOPER] gardenlogin is using go1.20 now. Make sure to upgrade your go installation if not already done. (gardener/gardenlogin#45, @petersutter)

✨ New Features

• [USER] client.authentication.k8s.io/v1 is now supported (gardener/gardenlogin#43, @petersutter)

🏃 Others

• [DEVELOPER] Go module dependencies were updated to latest version (gardener/gardenlogin#36, @petersutter)
• [DEVELOPER] The golang version to build the binaries is upgraded to v1.20.2 (gardener/gardenlogin#45, @petersutter)

v0.3.0

[gardenlogin]

🐛 Bug Fixes

• [USER] Fixed an issue where gardenlogin would report that no matching cluster could be found for server and certificate-authority-data in case the Shoot cluster CA is being rotated (gardener/gardenlogin#29, @petersutter)

v0.2.0

[gardenlogin]

✨ New Features

• [USER] You can now override the current context of the garden cluster kubeconfig by setting the gardens[].context property in your gardenlogin config file. (gardener/gardenlogin#24, @petersutter)
• [USER] Add klog flags like v (gardener/gardenlogin#21, @petersutter)
• [USER] If no configuration file is found, it falls back to the gardenctl-v2 configuration file (~/.garden/gardenctl-v2.yaml) which shares the same configuration properties (gardener/gardenlogin#20, @petersutter)

🐛 Bug Fixes

• [USER] Fixed an issue when switching to the *-internal context (no matching user config found for user name garden-myproject--mycluster-internal) (gardener/gardenlogin#23, @petersutter)

🏃 Others

• [USER] ⚠️ the configuration properties have changed to align with gardenctl-v2. Please rename your configuration properties accordingly as they may not be supported with future gardenlogin releases: (gardener/gardenlogin#20, @petersutter)
  • gardenClusters was renamed to gardens
  • clusterIdentity was renamed to identity

v0.1.5

no release notes available

v0.1.4

no release notes available

v0.1.3

no release notes available

v0.1.2

no release notes available