Today’s blog post is about the awesome IBM Garage Cloud Native Toolkit to support continuous integration and continuous delivery (CICD).
I want to provide a basic overview from my perspective, which I structured in following sections:
Ask your human Operator to do all the complicated ugly work for you!
… or write your own Operator, if you are the expert and you know how the complicated ugly work, works in detail. This is how you can make sure it works in the future 😉
For those of you who don’t know Kubernetes Operators in combination with Ansible, let me just give you a very simplified description from my point of view:
Even a student with minimal knowledge of Kubernetes should be able to install a highly complex container-based application on top of Kubernetes or OpenShift. Eliminate the manual interaction effort as much as possible to deploy, run, and maintain your containerized application on Kubernetes or OpenShift with your Operator implementation.
During my search on the internet, how to build an own custom Kubernetes Operator, I came along to that awesome YouTube video with a talk from Keith Tenzer, he gave in 2020 on the Open Infrastructure Foundation Summit called “Building Kubernetes Operators with the Operator Framework and Ansible”.
In this blog post I want to point out that I created a 18 min YouTube video related to the newly created workshop Get started with security for your Java Microservices made by Harald, Niklas and me .
I focus in that video on the topics authentication and authorization for Java Microservices with Keycloak, Quarkus and Microprofile. Have fun 😉
Select your starting point for the video:
The workshop documentation with MkDocs:
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
#Authorization, #Authentication, #Java, #Microprofile, #Quarkus, #Keycloak
In this blog post I want to point out that I noticed that the IBM Cloud Container Registry is deprecating container builds.
If you don’t know the IBM Cloud Container Registry here are some useful features:
In this blog post I want to highlight the news, that our tutorial Get your Java Microservice up and running is now available on IBM Developer.
After you complete this workshop, you will:
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
#Java, #Microprofile, #Kubernetes, #Docker, #IBMCloud
In this blog post I want to highlight the hands-on workshop “Get your Java Microservice up and running!“, now available in GitBook . That workshop demonstrates how to build a Microservice with Java and how to deploy the Microservice Kubernetes on the IBM Cloud. The Microservice in this workshop is kept as simple as possible, so that it can be used as a starting point for other Microservices. The Microservice has been developed with Java EE, OpenLiberty and Eclipse MicroProfile.
The workshop is a part of the open source project Cloud Native Starter, which contains sample code that demonstrates how to get started with cloud-native applications and Microservice based architectures.
The Workshop has a related badge called Cloud Native Starter Level 1. This badge is available at Acclaim. In the related quiz you can verify your knowledge you achieved in the workshop.
The gif below show some major steps in the hands-on workshop. You will develop locally a Java Microservice and deploy that Microservice to a free Kubernetes Cluster on IBM Cloud.
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
#microprofile, #java, #ibmcloud, #openliberty, #microservices, #kubernetes
In this blog post I want to point out that I just created a 5 min YouTube video related to the great Hands-on workshop: Reactive Endpoints with Quarkus on OpenShift. In that short video I show the setup of the example application to show reactive programming.
The image below shows the major architecture of the reactive programming example. There are three Java Microservices, one Vue.js UI application and two infrastructure components running on OpenShift (Kubernetes).
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
PS: You can try out Cloud Foundry Apps or Kubernetes on IBM Cloud. By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.
#IBMDeveloper, #IBMCloud, #OpenShift, #Kafka, #Postgres, #MicroProfile, #Java #reactive
This blog post is about a very small, but useful change in the IBM Cloud CLI for Kubernetes clusters.
You no longer need to export and set the KUBECONFIG environment variable to access your Kubernetes cluster on IBM Cloud in a terminal session. ( IBM Cloud documentation ).
You just can execute following IBM Cloud CLI command,
ibmcloud ks cluster config --cluster YOURCLUSTER
and verify the config settings.
kubectl config current-context
| Before | Now |
|---|---|
 |
 |
That’s all.
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
PS: You can try out Cloud Foundry Apps or Kubernetes on IBM Cloud. By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.
#IBMCloud, #Kubernetes
error: unable to recognize "deployment.yaml":
no matches forkind "Deployment"in version "apps/v1beta1"
Note: Additional useful blog post here.
error: error validating "deployment.yaml": error validating data: ValidationError(Deployment.spec): missing required field "selector"in io.k8s.api.apps.v1.DeploymentSpec; #if you choose to ignore these errors, turn validation off with --validate=false
kind: Deployment apiVersion: apps/v1 metadata: name: authors labels: app: authors spec: selector: matchLabels: app: authors version: v1 replicas: 1 template: metadata: labels: app: authors version: v1 spec: containers: - name: authors image: authors:1 ports: - containerPort: 3000 ... |
kind: Deployment apiVersion: apps/v1beta1 metadata: name: authors labels: app: authors spec: ... ... ... ... replicas: 1 template: metadata: labels: app: authors version: v1 spec: containers: - name: authors image: authors:1 ports: - containerPort: 3000 ... |
I hope this was useful for you and let’s see what’s next?
Greetings,
Thomas
PS: You can try out Cloud Foundry Apps or Kubernetes on IBM Cloud. By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.
#Kubernetes, #Deployment, #yaml
In that blog post I want to point out the awesome topic, how to automate the deployment of a Microservice using a delivery pipeline on IBM Cloud.
Maybe you already know Niklas, Harald and I made the great project called Cloud Native Starter. That project includes a Hands-on workshop that is called “Build a Java Microservice and deploy the Microservice to Kubernetes on IBM Cloud”. In Lab 4 you have to deploy the Authors Microservice to Kubernetes on IBM Cloud. Sometimes we have limited time in workshops. The limited time is the reason why we want to reduce the manual effort for students in a workshop to a minimum, therefor we took the IBM® Cloud Continuous Delivery and I created a repeatable way with minimal human interaction. The delivery pipeline contains sequences of stages which retrieve inputs and run jobs, such as builds, and deployments.
That image shows two stages, one stage is called FETCH and the other DEPLOY_SERVICES. The FETCH stages contains a job called Fetch code and the DELOY_SERVICES has two jobs one for build and one for deployment.
With the realization of the automated setup for the creation of the toolchain, you can just press the button Create toolchain in the GitHub project and follow a guided wizard to deploy the Authors Microservice.
Visit the hands-on workshop Use a IBM Cloud toolchain to deploy a Java Microservices to Kubernetes on IBM Cloud and press the button 😉
