Cover photo by Alex Wong on Unsplash.
In a previous post I described the rationale behind our decision to abandon the secureCodeBox v1 and redesign the whole architecture. In this post I'll go into the details of this redesigned architecture.
Cover photo by Evan Dennis on Unsplash.
In this article I will give you a deeper insight why we decided to make a major breaking rewrite of the secureCodeBox. First I'll give you an overview of the v1 architecture and the rationale behind. Also outline the problems we stumbled upon using secureCodeBox v1 for some years now. Afterwards I introduce you to the new secureCodeBox v2 architecture and the rationale behind.
As documented we only support the latest four releases of Kubernetes. This means we removed support for Kubernetes 1.16 with the secureCodeBox release 2.3.0.
If you rely on that particular version of Kubernetes, we may help you with custom paid support. Please contact us via email or open an GitHub issue.
(Photo by Elisha Terada on Unsplash)
We are very happy and proud to announce the release version 2.0.0 of secureCodeBox. It is a better, faster and greater secureCodeBox since ever 馃榾
Photo by Javier Allegue Barros on Unsplash.
Maybe you're wondering what's going on with my beloved secureCodeBox. If you look at the GitHub insights for the main repo, you'll see: Not that much is going on:
So is secureCodeProject dead? Of course not! But we gained a lot of experiences using secureCodeBox and went through some changes in the last couple of months. In this blog post, I'll give you a brief outline of all these changes and what we aim to do in the near future.