Using the internal OpenShift container registry to deploy an application

This cheat sheet is an extension to a blog post I made which is called: Configure a project in an IBM Cloud Red Hat OpenShift cluster to access the IBM Cloud Container Registry . In that related blog post we used the IBM Cloud Container registry to get the container images to run our example application. Now in this cheat sheet we will use the Red Hat OpenShift internal container registry and the Docker build strategy to deploy the same example application to OpenShift.

How to use environment variables to make a containerized Quarkus application more flexible

When you run a containerized application on a container orchestration platform like Kubernetes, Open Shift or with a serverless framework like Knative or Code Engine or on other platforms, it is helpful to pass endpoints to other applications to the containerized application by using environment variables. When the container will be restarted, these variables can be provided to the container and no adjustment in the source code is necessary. You can use configmaps or in Code Engine simple the environment variable itself.

Build a Docker image, push it to Docker hub and clean up local disk space

This blog post does contain the tasks to create a Docker image and upload the image to dockerhub and clean up the image and container on the local machine. Upload the image 1. Create a local Docker image using docker build Dockerhub account name: tsuedbroeckerDockerhub repository name: cns-workshop-toolsTag: v4Docker image name with tag: tsuedbroecker/cns-workshop-tools:v4 docker... Continue Reading →

Blog at WordPress.com.

Up ↑