Skip to content

Releases: sky-uk/osprey

v2.7.0

18 Feb 14:36
0e3da3e
Compare
Choose a tag to compare

Changelog

v2.6.0

25 Nov 09:30
8c1abbb
Compare
Choose a tag to compare

Changelog

  • 5d411c4 Add goreleaser (#72)
  • 8c1abbb Fetch API server URL from GKE OIDC ClientConfig (#73)
    This allows osprey client to fetch the API server URL from the kube-public/ClientConfig resource. This is created when the OIDC Identity Service is enabled in GKE
  • 47439f3 Some fixes (#63)
  • d5795a3 Update dependencies (#71)

v2.5.0

28 Sep 13:28
61390f7
Compare
Choose a tag to compare
  • Add ability for osprey client to fetch the API server CA from the API server itself, rather than needing an osprey server deployment to serve it. #69

This is controlled by a new api-server field in the Osprey config file. The target Kubernetes cluster must have the feature gate RootCAConfigMap enabled. It was introduced in v1.13 and became enabled by default in v1.20.

RootCAConfigMap: Configure the kube-controller-manager to publish a ConfigMap named kube-root-ca.crt to every namespace. This ConfigMap contains a CA bundle used for verifying connections to the kube-apiserver. See Bound Service Account Tokens for more details.

Anonymous access needs to be enabled for the API server and a suitable RoleBinding in place to allow access to system:anonymous users.

apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: anonymous-kube-root-ca
  namespace: kube-public
rules:
- apiGroups:
  - ""
  resources:
  - configmaps
  resourceNames:
  - kube-root-ca.crt
  verbs:
  - get
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: anonymous-kube-root-ca
  namespace: kube-public
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: anonymous-kube-root-ca
subjects:
- apiGroup: rbac.authorization.k8s.io
  kind: User
  name: system:anonymous

v2.4.0

19 Nov 18:11
25802a9
Compare
Choose a tag to compare
  • Conform to XDG standards for configuration #55
  • Add username/password command line options for Osprey login #57
  • Fix readme: osprey ca configuration #59

v2.3.0

27 Feb 15:17
dac93ee
Compare
Choose a tag to compare
  • Automatically close browser window if possible (#53, #54)

v2.2.0: Automatic browser popup for OIDC login

07 Feb 11:27
f03f904
Compare
Choose a tag to compare
  • Add automatic browser popup for OIDC login (#52)
  • Remove Bintray's latest artifact generation (#49)
  • Readme typo-fix issue #50 (#51)
  • Fix error message (#48)

v2.1.0

06 Nov 08:52
bcd84fe
Compare
Choose a tag to compare
v2.1.0

v2.0.0: Support AzureAD (#36)

09 Aug 13:09
a9a567c
Compare
Choose a tag to compare

Release 2.0.0

  • Adds support for authentication using Azure Active Directory as the OIDC.
  • This release introduces a breaking change to osprey config files. This is due to functionality to support multiple
    identity providers in the same configuration file.