v0.1.0

v0.1.0 (2021-08-23)

Welcome to the first minor release of Capsule full of new features!

⚠️ Warning: this release contains breaking changes!

Docker images are hosted on quay.io and can be pulled with the following command:

docker pull quay.io/clastix/capsule:v0.1.0

Enhancement

• Use more comprehensive variables in the code-base (#164)
• Releasing Helm chart release upon tag (#250)
• Use multiple groups as capsule-user-group (#258)
• Support of Capsule Chart for ArgoCD (#266 #264)
• ⚠️ Webhook refactoring (#297)
• Optimizing reconciliations for RoleBinding (#315)
• Refactoring of the Tenbant controller (#363)

Breaking changes

• ⚠️ Removing the RBAC Proxy sidecar container for metrics exposure (#246)
• ⚠️ Capsule configuration using the CapsuleConfiguration CRD (#122)
• ⚠️ Dropping for v1beta1 additionalPrinterColumns regarding tenant ownership (#331)
• ⚠️ Preventing ingress hostname collision by default (#218 #207)

Hotfix

• Using an arbitrary name for capsule namespace generates errors during webhook calls (#247)
• Check for KUBECONFIG env variable during user creation (#298)
• ⚠️ Wrong package name for the config controller (#373)
• Documenting Helm Namespace creation (#359)
• Documenting Capsule installation on AWS EKS (#306)

Features

• Support for armv7/arm64 (#244)
• Emitting events for policy violations and other events (#173)
• Support for ImagePullPolicy enforcement at Tenant level (#271)
• Tenant cordoning (#243)
• Grafana dashboard (#150)
• Single YAML file installer (#347)
• Support for Service type enforcement at Tenant level (#339 #390)
• Support for PriorityClass enforcement at Tenant level (#257)
• ResourceQuota scope configurable at Tenant level (#50)
• Support up to Kubernetes 1.22 (#335)
• Addressing the multi-tenancy benchmark requirements (#68)
• Ingress hostname collision scope, evaluating Ingress paths (#358)
• New Capsule v1beta1 API version (#286)
• Support for multiple Tenant owners (#276)
• Tenant backup and restore of a Tenant using bash script (#320 #338)

More features are on their way and planned here.

Thanks

For our biggest release, many kudos to the great effort showed by @MaxFedotov, @alegrey91, @ptx96, @spagno, @viveksyngh, @sftim, @xphoniex, @ruzickap, @ludusrusso, and @bsctl.