Kubernetes

Following on the Using Kcli to prepare for OCM testing, we’re going to prepare KMM testing in Hub-Spoke approach. First we need to prepare our .docker/config.json with the contents of our OpenShift pull secret used with Kcli. mkdir -p ~/.docker/ cp openshift_pull.json ~/.docker/config.json Warning advisories Note Semi-scripted version available at automate.sh Warning We’re using pre-release bits of the software, that’s why we need to define a custom catalog for both the Hub and the Spokes. Once KMM is released it will be available from the official one and just the Policy will be needed. ...

Kcli allows to quickly interact with different virtualization platforms to build machines with some specific configurations, and via the use of plans it allows to automate most of the setup required to have an environment ready. In our case, let’s setup an environment to practice with Open Cluster Management but instead of using kind clusters, let’s use VM’s. Note We’ll require to setup an openshift_pull.json file for Kcli to consume when accessing the required resources for this to work. That file, contains the credentials for accessing several container registries used for the deployment. ...

In order to setup disconnected registry for installation, follow this blog post by Daniel at Introducing Mirror Registry for Red Hat OpenShift. At the end of the process it will output something like: INFO[2022-08-19 07:10:22] Quay installed successfully, permanent data is stored in /etc/quay-install INFO[2022-08-19 07:10:22] Quay is available at https://${HOSTNAME}:8443 with credentials (init, ${PASSWORDSTRING}) Once the setup is done, remember several steps: Edit /etc/containers/registries.conf to add relevant entries for our registry as required: ...

During the last months, I’ve been working with my colleagues on setting up a workflow that can be used to deploy Spoke clusters in an automated way. More or less, the idea behind this is that a cluster is configured via a set of configuration files and templates so that the required components are installed: Advanced Cluster Management (ACM) Quay registry OpenShift Data Foundation OpenShift Pipelines (a.k.a. Tekton) etc Once the system was configured, it would become a ‘Hub’, and from it, several ‘Spokes’ could be deployed using ACM, getting them configured in the process to become a cluster suitable for fully-disconnected operation. ...

Introduction In a regular OpenShift environment, NTP server is more less like this: Diagram In a self-contained cluster with no connection to external networks NTP server is not reachable, but a reachable NTP server is required for proper cluster synchronization. Cluster does use SSL certificates that require validation and might fail if the dates between the systems are not in sync or at least pretty close in time. Diagram We’ve several components already available in our OpenShift cluster that are very useful: ...