Get off to a flying start with Kubernetes and take the Kube Challenge
As a popular open source platform for managing applications in containers, Kubernetes brings many advantages. But how do you start as an organization? Take the Kube Challenge!
In the previous blogs about Kubernetes, we described the origin history of the platform, the various reasons for using it to manage and control applications and to set up the innovation process as a necessary environment variable for containers. In particular, the latter aspect – the organizational part – appears to be a difficult hurdle in practice for organizations that want to innovate faster, more cheaply and more safely. This is mainly psychological, because changes are not necessarily as big as people often seems to think.
What’s your challenge?
To encourage people to work with microservices in containers, we created the Kube Challenge at MatrixMind. Organizations that take up the challenge will therefore eliminate all environmental factors that hamper innovation. In a short two-week sprint, they focus on achieving a small change that will enable them to achieve results quickly.
Many companies have fantastic business cases where such an approach is worth its weight in gold. Think, for example, of replacing paper letters with PDFs for informing customers. The savings resulting from this can be calculated quickly. Ideally, you would divide such a change into small blocks, with two-week sprints. A problem that many change processes have to deal with is that their scope often expands further and further, which means that the duration of the process quickly increases sharply. So look for “little cubes.” In the case of replacing letters with PDFs, it is not necessary initially to deal with all customer communication. Select one particular customer letter, for example a payment reminder. Then see how many of these letters you can “get rid of” in two-week sprints. Each cube that you remove as a microservice is one. Pure profit.
Start of a continuous innovation cycle
This is exactly the process that the Kube Challenge helps with. We also realize that the challenges are broader than just the technology. In the case of the customer letter, marketing will also have to be involved and a copywriter will be put to work. They are also asked not to describe the overall problem, but to deal with one small block. In the meantime, the Kube Challenge helps to describe the problem to the business. With Kubernetes, IT ensures a runtime environment, connects it to the IT infrastructure and from this basis a multidisciplinary team connects the challenges together within the organization. This creates innovatuon loop, which always leads to the next improvement.
The Kube Challenge is of course named after Kubernetes. This platform brings together all the new developments. Organizations can innovate in small blocks (microservices) and then scale up unlimited, with the pay-as-you-go nature of the cloud being a major advantage. Innovation is also relatively risk-free in this way, as a new innovation cycle begins every two weeks. It is also still possible to start again, without wasting a lot of time and money. This takes the financial pressure off the innovation process. And because microservices in containers are “portable,” it doesn’t matter in which environment they run: in the public cloud, a private cloud or visualized in an on-premises environment.
A challenge for every company
Who is the Kube Challenge for? Many companies are traditionally not IT companies. In the meantime, we are emerging from the trend in every sector towards converging software, physical products and services. As a result, many companies are facing a transformation step. This applies to large enterprise organizations, but also to an increasing number of organizations in the medium-sized business sector. Take, for example, an elevator manufacturer who sees software playing an increasingly important role in its physical products. They also have to make the transformation into a “software house.” This is exactly where the Kube Challenge helps. Software has become part of the production process and taking up the challenge is an incentive to better integrate it.