Containers

The terms "serverless" and "Function as a Service" (FaaS) often are used interchangeably, but they do not mean the same thing. This article describes the terms and how Knative is speeding the evolution of both by enabling any service to be available as a function.

Get a basic understanding of containers and images, so you can start using them successfully in a production environment.

This article provides tips that will make life easier when you install OpenShift 4.0 Developer Preview on Amazon Web Services (AWS).

How to build a Java 8 runtime image with Docker and also with Buildah. Deployment to OpenShift is also shown by pushing the image to Quay and importing the stream.

What docker users need to know to move from Docker to Podman and Buildah and the advantages of doing so. Developers/operators can easily move to Podman, do all the fun tasks that they are familiar with from using Docker, and do much more.

Get started with an introduction to container architecture including engine, image, registry, volume, related commands.

To learn more about OpenShift without needing to install it yourself you can use the interactive lessons or try our new developer sandbox.

Part 1 of a two-part series, explores techniques that enable the portability of containers across different environments.Through these techniques, you may be able to use the same language, framework, or tool used in your datacenter straight to the IoT edge, even with different CPU architectures.

Kubernetes may be the new application server for some, but not all Java apps. This article discusses the choices: traditional app servers, "just enough app server" choices like Thorntail, and Kubernetes.

Learn how containers and Kubernetes have changed development process and

The ability to generate Kubernetes YAML from Podman is under development. Podman can now capture the description of local pods and containers and then help users transition to a more sophisticated orchestration environment like Kubernetes. This article provides a demo to illustrate the process.

Learn how to create, develop, and run Sping Boot based Camel/Red Hat Fuse projects using VS Code. You will be able to run locally or deploy to Red Hat OpenShift.

Part 6 of Eric Schabell's integration series covers the storage elements of a generic architectural blueprint for the omnichannel customer experience use case.

Part 3 of a series about using a container platform for automated performance testing. It covers how to automate and orchestrate the provisioning of an environment and the execution of performance tests.

The pod concept for containers was introduced in Kubernetes. Podman lets you manage pods locally, giving it an advantage over other container runtimes.

This article, which is Part 5 of the series, covers core elements of a generic architectural blueprint (container platform and microservices) for the omnichannel customer experience use case.

Part 2 of a series about using a container platform for automated performance testing. It describes how to build an observability stack that can be used during automated performance tests.

Learn how to instrument and monitor Node.js applications on OpenShift with Prometheus. Increase observability of your microservice deployments.

This article, which is Part 4 of the series, covers details pertaining to API management and reverse proxies of a generic architectural blueprint for the omnichannel customer experience use case.

Video: Security Considerations for Container Runtimes. Explains/demonstrates using Kubernetes with different security features for your container environment.

This article discusses a fast and easy way to get Java apps running in a cloud by using OpenShift’s Source-to-Image (S2I) builder with Maven, Gradle,or Java 11.

This article, which is Part 3 of the series, covers details pertaining to the specific elements (mobile and web application deployments) that can be used in a generic architectural blueprint for the omnichannel customer experience use case.

This article describes how to build .NET Core container images using source-to-image (S2I). The container images can be built directly from a git repository, from local sources, or from a pre-built application on, which can be useful on your development machine or as part of a CI/CD pipeline.