Categories
00 - Cloud-Native App Dev development

Cloud Native AppDev without Tears – Using odo to Boost your Workflow

Traditionally application development and deployment across environments has been very tedious and error prone. For example in the Java world you would work with different packaging formats such as ears, wars and jars each with environment specific configuration usually dispersed all over the place. Then your app might behave differently on each operating system due […]

Categories
00 - Cloud-Native App Dev

How to go from Docker to Kubernetes the right way

Docker came a long way. It established itself very fast as the de-facto standard to get going with your container journey. It did not matter if you wanted to just play around with containers or if you wanted to build up new microservices, Docker was and still is a great choice to get yourself started. […]

Categories
00 - Cloud-Native App Dev

How to pimp your Quarkus application to benefit from Kubernetes

In my last post I promised to introduce you to a selected set of Quarkus extensions. Today I will cover three of those. In my opinion they make total sense in the context of a container development or just container runtime platform (such as Red Hat OpenShift or any other Kubernetes distribution). The effort : […]

Categories
00 - Cloud-Native App Dev

How to accelerate your cloud-native AppDev with knative Java and OpenShift

Quarkus is the bright new star in the cloud-native App Dev universe! Quarkus is Red Hat’s upstream stack for Kubernetes native Java. Its characteristics are simple: Quarkus is small! Quarkus is fast! Quarkus is familiar! … and Quarkus makes Java relevant again in the cloud-native world where everyone talks about lightweight architectures, event-driven paradigms, container […]

Categories
Containers Kubernetes Networking OpenShift Uncategorized

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 6: CONTROLLING EGRESS TRAFFIC

OpenShift 3.3 and later contain the functionality to route pod traffic to the external world via a well-defined IP address. This is useful for example if your external services are protected using a firewall and you do not want to open the firewall to all cluster nodes. The way it works is that a egress […]

Categories
Containers Kubernetes Networking OpenShift Uncategorized

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 5: OPENSHIFT ROUTER

In the OpenShift world, Services take place on the OSI Layer 3 / IP, while Routing is an OSI Layer 7 / HTTP/TLS concept. Once you’ve wrapped your head around this backwards choice of naming, things are fairly easy: An OpenShift Router is a component which listens on a physical host’s HTTP/S ports for incoming […]

Categories
Cloud Containers OpenShift Technology

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 4: CONTAINER NETWORKING USING OPENSHIFT/KUBERNETES SERVICES

To allow stable endpoints in an environment of ever changing starting and stopping Pods (and therefore constantly changing IP addresses), Kubernetes introduces (and OpenShift uses) the concept of services. Services are stable IP addresses (taken per default from the 172.30.0.0/16 subnet) that remain the same as long as the service exists. Connection requests to a […]

Categories
Cloud Containers OpenShift Technology Uncategorized

OPENSHIFT NETWORKING FROM A CONTAINER/WORKLOAD POINT OF VIEW – PART 3: CONTAINER NETWORKING ACROSS OPENSHIFT NODES

So far, this sounds like a lot of effort to achieve a little more than a plain docker host – containers that can talk to each other and to the host network, potentially segregated based on kubernetes namespace. However OpenShift SDN also allows pods on different nodes to communicate with each other. To this end, […]