Over the past few months, the Bitnami team has been working on adding features to Kubeapps such as the ability to rollback releases and to customize private Helm registries. This new release adds to these improvements with support for two major new features: Forms to deploy and upgrade applications and OIDC support with OAuth2_proxy.
Keep reading to discover these new features and how to start using them.
Simple Forms to Deploy and Upgrade Applications
It is now possible to change the default chart configuration for new deployments easily. This feature is already active for the stable versions of WordPress, PostgreSQL, and Apache, and there are more to come!
By clicking the Deploy button for those charts, a new form is displayed. This form allows you to change common parameters, such as the username or password, without the hassle of knowing how the values.yaml file of the chart is structured.
With this new feature, it’s even easier to adopt Kubernetes applications that are ready for production. Watch the following video to learn how to deploy WordPress after modifying the default values:
How can you add this form to your chart?
With Helm v3, you can include a JSON Schema along with your chart. This file is named values.schema.json and it allows you to describe the content of the values.yaml file. The goal of this new file is to verify that the chart values satisfy the expected structure, but Kubeapps also uses it to render the form mentioned in the section above. With some special annotations, you can specify which parameters should be present, so Kubeapps can render it. To learn more about this feature, check the Kubeapps developer documentation.
OIDC Support with OAuth2_proxy
Some time ago, we started to support OpenID Connect (OIDC) as an alternative to the default login experience in Kubeapps. If you enable it, you can login in to Kubeapps with an email account using the identity provider of your choice, such as Google or GitHub:
By installing Kubeapps v1.6.0, you can now configure OIDC to work with more managed platforms for Kubernetes, like GKE, thanks to oauth2_proxy . But remember, if you were using OIDC in previous versions of Kubeapps, you will need to change some of the chart parameters to enable this feature. Check out these instructions to learn how!
By installing Kubeapps v1.6.0, you can now configure OIDC to work with more managed platforms for Kubernetes, like GKE, thanks to oauth2_proxy . But remember, if you were using OIDC in previous versions of Kubeapps, you will need to change some of the chart parameters to enable this feature. Check out these instructions to learn how!
We would like to hear about your experience with the new version of Kubeapps. You can reach out to the Kubeapps team both through our GitHub page and through the #kubeapps channel in Slack.
Happy Helming!