This blog post covers the topic connect to a PostgreSQL database, create tables, insert data and use a file from a GitHub project and do the implementation with GO. That blog post is also related to my last blog post called Connect to a PostgreSQL database using GO. You find the related code to my new blog post in that GitHub project.
Connect to a PostgreSQL database using GO
This blog post is related to this good pgx - PostgreSQL Driver and Toolkit that is used to access a PostgresSQL database with GO. My blog post contains minor modifications of an example in that toolkit. You can find the source code related to my blog post in that GitHub project.
Develop a simple operator to deploy a web application using the GO Operator SDK
This blog post is a bigger cheat sheet about how to start with an operator implementation with the GO Operator SDK and also contains some details how to define Kubernetes deployments, secrets, and services.
Let’s get started with the development of operators using the GO SDK
That new blog post is related to start with development of operators using the GO API. I want to point to some resources which are from my personal perspective are an incredible combination to start and I want to highlight some major points which are relevant in that context.
FATA[0009] failed to create API: unable to run post-scaffold tasks of “base.go.kubebuilder.io/v3”: exit status 2
This blog post is about how you could save time, when you are starting to setup your development environment for a GO operator with the Operator SDK on a macOS, in combination with Visual Studio Code.
New Open-Source Multi-Cloud Asset to build SaaS
When software is provided as a managed service (SaaS), using a multi-tenant approach helps minimise costs for the deployments and operations of each tenant. In order to leverage these advantages, applications need to be designed so that they can be deployed to support multiple tenants, while maintaining isolation for security reasons. At the same time, common deployment and operation models are required so that new SaaS versions can be deployed to existing tenants, or to onboard new tenants, in a reliable and efficient way.
Instantiation of a Red Hat OpenShift cluster in a Multizone VPC IBM Cloud environment using the free IBM Cloud Schematics (“Terraform as a Service”)
In this blog post we will look at the steps we need to do, when we use IBM Cloud Schematics service with Terraform to instantiate a Red Hat OpenShift cluster in a "Multizone VPC IBM Cloud environment".
Create a ssh key for your GitLab project on IBM Cloud
This blog post is a short cheat sheet to remember how to configure the access to a GitLab project on IBM Cloud from a local computer. An important part in that situation is you need to configure a ssh key for your computer and save this key in GitLab on IBM Cloud. The remaining parts is how … Continue reading Create a ssh key for your GitLab project on IBM Cloud
Example usage of the internal IBM Cloud GitLab instance
This is a simple cheat sheet which has these two simple objectives: How to create a group in this GitLab instance and add a member.How to create a project for that group. You need an IBM Cloud Account to access the internal IBM Cloud GitLab and you need to see this in context with the … Continue reading Example usage of the internal IBM Cloud GitLab instance
Update a master node of an OpenShift cluster on IBM Cloud
This small cheat sheet is about "how you update a master node of an IBM Cloud OpenShift cluster" and it is also related to an older blog post I wrote called Using a Red Hat OpenShift cluster on IBM Cloud some basic thoughts. (Link to the IBM Cloud documentation) Step 1: Login to your IBM Cloud account where … Continue reading Update a master node of an OpenShift cluster on IBM Cloud