Use Software Everywhere and IasCable to setup GitOps on a Red Hat OpenShift Cluster in a Virtual Private Cloud on IBM Cloud

This is a long blog post and the third one related to the Software Everywhere project and IasCable. Our objective in this blog post is to create a customized initial GitOps setup in an IBM Cloud environment. The Software Everywhere project and IasCable CLI do provide an awesome way to eliminate writing Terraform modules for various clouds such as IBM Cloud, AWS or Azure to create and configure resources. We are going to reuse Terraform modules which the Software Everywhere catalog does provide.

2

“AWS CLI: command not found on” macOS

I had following terminal output "zsh: command not found: aws" after the installation of the AWS CLI on macOS, because AWS CLI uses python and you need to ensure you did configure python right. That make it a little-bit more tricky for me to install that CLI on my machine, compared for example to the IBM Cloud CLI.

0

Bash scripting to ensure Kubernetes resources are deleted in synchronization

Sometimes we need to ensure that resources in Kubernetes are fully deleted before we setup other resources. In Kubernetes the timing and the synchronization can be very import and relevant. In that blog post we see a function of a bash script, that exactly does that job for namespaces. We are using a “for loop” combined with a nested “while loops” and other functionalities in bash to address that topic.

3

Get your custom logs of your operator

That blog post is about an easy example to get your custom logs of your operator, when the operator is running on a Kubernetes cluster. That blog post does reference an example GitHub project called Example Tenancy Frontend Operator you can use to verify the steps. (branch monitor-grafana-operator) In this project I wrote a short custom logging that... Continue Reading →

0

Blog at WordPress.com.

Up ↑