Kubernetes, also known as K8s has become the de facto platform for orchestrating modern microservices architectures, promising resilience, scalability and faster deployment pipelines for Java applications. But for many developers, that promise often hides a thorny reality: Kubernetes is powerful—but also painfully complex.

Almost any developer looking to leverage containers turns to Kubernetes (K8s) for orchestration. However, with its complexity comes security risks, particularly misconfigurations, which remain one of the most critical attack vectors in cloud-native environments. In effect, K8s misconfigurations can lead to data breaches, privilege escalations and service disruptions. 

This blog examines key technical security challenges associated with K8s and demonstrates how to mitigate these risks through platform engineering. 

Start-ups are hotbeds of innovation, where speed, agility and resourcefulness are key to success. But in the world of enterprise Java applications, managing complex cloud deployment infrastructure can quickly become a bottleneck and take up considerable time from your developers. To address these issues and streamline cloud deployments, we created Payara Cloud.

Kubernetes is a topic that is frequently discussed in the development community, especially as the IT landscape increasingly shifts towards cloud and microservices. However, it’s crucial to evaluate whether it is genuinely indispensable for your environment or just another case of the next 'new and shiny' object capturing attention without substantial benefits. In this blog, we’ll delve into the reasons why Kubernetes might sometimes fall victim to the hype and explore whether it is the right fit for all scenarios. 

These days, it seems Kubernetes is a topic that is never too far from people's lips.  The tool, and the associated tools built around it, are talked about so often it seems it's the only subject important to developers these days - especially as the IT world becomes increasingly orientated towards cloud and microservices.

But in spite of all the conversation around Kubernetes... do you really need Kubernetes for your environment? Or is it just another case of the next 'new and shiny' object,  with people distracted by the novelty and possibility, rather than the facts? In this blog, I'll take a closer look at why Kubernetes might be a case of the hype outweighing the helpfulness in most cases. 

In this day and age, securing enterprise platforms is a challenge that developers and consultants tackle in an uninformed manner, producing subpar solutions in most cases. To combat this pattern, third-party security services such as Auth0 have been devised to externalize the security of services, and they focus on stable implementations of common enterprise use cases (identity management, OAuth compatibility, and so on), and platforms such as Eclipse MicroProfile allow for their easy integration with enterprise Java microservices. Moreover, in combination with Kubernetes, MicroProfile is a very powerful tool to simplify securing microservices, monitoring them and creating reproducible deployments.

Introduction

With Container orchestration tools like Kubernetes and Docker Swarm, you can add instances quite easily. Depending on the type of clustering you need or use for your application, some scenarios are easier to implement than others.

Introduction

Application updates are required as part of the normal maintenance process of your application lifecycle management. These updates should be as smooth as possible, and especially for a micro-services environment, performed with zero-downtime of your Payara Micro application. The Kubernetes Rolling Upgrades feature can help you with this.

In this blog, I'll discuss the basics around Kubernetes ConfigMaps and Secrets and give two examples of how you can use them in combination with Payara Micro.