Red Hat Logo

Steps to replace nip.io with xip.io in CDK/Minishift

If you’re a Red Hat Container Development Kit (CDK) or upstream Minishift user, you would have been affected by the unavailability of nip.io. When you create a route for an application running in OpenShift (provided by Minishift) it uses nip.io for routing to the Minishift VM IP address. As a result, it is impossible to access the route created with nip.io suffix.

Continue reading Steps to replace nip.io with xip.io in CDK/Minishift

Share

HOW-TO setup 3scale OpenID Connect (OIDC) Integration with RH SSO

This step-by-step guide is a follow-up to the Red Hat 3scale API Management new 2.1 version announcement. As many of you will know, this new version simplifies the integration between APIcast gateway and Red Hat Single Sign-On through OpenID Connect (OIDC) for API authentication. As a result, now you can select OpenID Connect as your authentication mechanism besides API Key, App Key pair, and OAuth. Also, the on-premise version adds a new component that synchronizes the client creation on the Red Hat Single Sign-On domain.

Continue reading “HOW-TO setup 3scale OpenID Connect (OIDC) Integration with RH SSO”

Share

Red Hat extends container development tooling with updated DevSuite, DevStudio, CDK

We’re extremely pleased to announce updates to our Red Hat Development Suite of products, including Container Development Kit 3.2, JBoss Developer Studio 11.1, OpenJDK 9 and our DevSuite 2.1 Installer. As always, our focus is on increasing usability for developers, while adding new features that matter for developers targeting Red Hat platforms.

Continue reading Red Hat extends container development tooling with updated DevSuite, DevStudio, CDK

Share
Dynamic Storage

How to configure persistent storage with OpenShift or Kubernetes for development environment

  • We know that containers in Openshift or Kubernetes don’t persist data. Every time we start an application, it is started in a new container with an immutable Docker image.
    Hence, any persisted data in the file systems is lost when the container stops. Hence if an application or container is rebuilt or restarted than we can’t view previous logs or if we are using containers with mysql or any other database then schema, tables, and all data will be lost, if using any messaging broker than if there is journal file than it will also not persist.
    Hence, these ephemeral containers cannot be used in production environment. In a production environment, we must configure a shared storage.
  • But what about the development environment, because we might not always have enough labs and VM’s available. To rescue we have volume type hostPath, which can be easily set up with Minishift and Minikube.
  • This article will provide details how to setup hostPath volume type.

Continue reading “How to configure persistent storage with OpenShift or Kubernetes for development environment”

Share

Gluster for OpenShift – Part 1: Container-Ready Storage

OpenShift Container Platform (OCP) offers many different types of persistent storage. Persistent storage ensures that data should be insistent between builds and container migrations. When choosing a persistent storage backend to ensure that the backend supports the scaling, speed, dynamic provisioning, RWX/RWO support and redundancy that the project requires. Container-Ready Storage (CRS), or native Gluster for OCP, is defined by the concept of persistent volumes, which are OCP created objects that allow storage to be defined and then used by pods to allow for data persistence.

Continue reading “Gluster for OpenShift – Part 1: Container-Ready Storage”

Share