This blog post is one example “how to setup an app-of-apps pattern in ArgoCD” and is in the context of the blog post How to use a declarative setup for Argo CD to deploy an application using a Helm repository?
In this blog post I will cover the topic, how to use Argo CD - Declarative Setup to deploy an application using Helm repository.
In this blog post I will cover the topic, how to use an existing Helm Chart project and an existing Argo CD instance on OpenShift to deploy an example application. The example application is a Node.js server application I used in several blog posts related to OpenShift. This blog post is in the context of my last blog posts using IasCable and Software Everywhere to setup GitOps. In this last blog post I showed how to setup Red Hat OpenShift and Argo CD and an initial GitOps repository on IBM Cloud and in this blog post we reuse the created environment with IasCable GitOps to create a new application inside Argo CD manually.
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.
In that blog post we use the IasCable framework to create a Virtual Private Cloud and a Red Hat OpenShift cluster on IBM Cloud. I covered the starting point for the IasCable framework in my last blog post “Get started with an installable component infrastructure by selecting components from a catalog of available modules with IasCable“
In that blog post we get started with the IasCable framework. The IasCable framework is a part of the Cloud Native Toolkit project with the objective to build an installable component infrastructure based on components from a catalog of available modules.
This blog post contains a simply example to create a Virtual Private Cloud and a Kubernetes Cluster on IBM Cloud using Terraform.
This blog post is about how to solve a problem when you try to execute a Jupyter Notebook on a 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.
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.