Skip to content

v0.6.0
Compare
Choose a tag to compare
@pinniped-ci-bot pinniped-ci-bot released this 11 Feb 16:19
v0.6.0
f015ad5
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release v0.6.0

Release Images

Image Registry
ghcr.io/vmware-tanzu/pinniped/pinniped-server:v0.6.0 GitHub Container Registry
docker.io/getpinniped/pinniped-server:v0.6.0 DockerHub

Changes

Breaking Changes

  • All concierge APIs are now cluster-scoped. This is a breaking change for the sake of API consistency. To upgrade Pinniped concierge, you must delete and recreate the concierge CRD objects. If you require a non-disruptive upgrade path, you can use the --api-group-suffix feature added in v0.5.0 to deploy multiple Concierge instances on the same cluster.

Minor Changes

  • All Pinniped APIs now use the status subresource functionality of Kubernetes API machinery.

  • The --concierge-namespace flag is now ignored and deprecated in the pinniped get kubeconfig and pinniped login CLI commands.

  • Upgraded Debian base images from 10.7 to 10.8.

  • Upgraded Go from 1.15.7 to 1.15.8.

  • Removed the pinniped get-kubeconfig and pinniped exchange-credential commands, which were deprecated in v0.3.0.

  • The kubectl get pinniped -A command no longer reports a "method not found" warning related to TokenCredentialRequest.

  • Updated default RBAC cluster roles to support Kubernetes flow control on clusters that have it enabled.

Diffs

A complete list of changes (40 commits, 243 changed files with 2,179 additions and 2,519 deletions!) can be found here.

Updates

The attached yaml files were updated on May 6, 2024 to use ghcr.io/vmware-tanzu/pinniped/pinniped-server instead of projects.registry.vmware.com/pinniped/pinniped-server.

Assets 9
Loading