#Openshift build trigger using openshift webhooks

[hawkstack]

🔧 Migrating from Jenkins to OpenShift Pipelines: 8 Steps to Success

As organizations modernize their CI/CD workflows, many are moving away from Jenkins towards Kubernetes-native solutions like OpenShift Pipelines (based on Tekton). This transition offers better scalability, security, and integration with GitOps practices. Here's a streamlined 8-step guide to help you succeed in this migration:

✅ Step 1: Audit Your Current Jenkins Pipelines

Begin by reviewing your existing Jenkins jobs. Understand the structure, stages, integrations, and any custom scripts in use. This audit helps identify reusable components and areas that need rework in the new pipeline architecture.

✅ Step 2: Deploy the OpenShift Pipelines Operator

Install the OpenShift Pipelines Operator from the OperatorHub. This provides Tekton capabilities within your OpenShift cluster, enabling you to create pipelines natively using Kubernetes CRDs.

✅ Step 3: Convert Jenkins Stages to Tekton Tasks

Each stage in Jenkins (e.g., build, test, deploy) should be mapped to individual Tekton Tasks. These tasks are containerized and isolated, aligning with Kubernetes-native principles.

✅ Step 4: Define Tekton Pipelines

Group your tasks logically using Tekton Pipelines. These act as orchestrators, defining the execution flow and data transfer between tasks, ensuring modularity and reusability.

✅ Step 5: Store Pipelines in Git (GitOps Approach)

Adopt GitOps by storing all pipeline definitions in Git repositories. This ensures version control, traceability, and easy rollback of CI/CD configurations.

✅ Step 6: Configure Triggers for Automation

Use Tekton Triggers or EventListeners to automate pipeline runs. These can respond to Git push events, pull requests, or custom webhooks to maintain a continuous delivery workflow.

✅ Step 7: Integrate with Secrets and ServiceAccounts

Securely manage credentials using Secrets, access control with ServiceAccounts, and runtime configs with ConfigMaps. These integrations bring Kubernetes-native security and flexibility to your pipelines.

✅ Step 8: Validate the CI/CD Flow and Sunset Jenkins

Thoroughly test your OpenShift Pipelines. Validate all build, test, and deploy stages across environments. Once stable, gradually decommission legacy Jenkins jobs to complete the migration.

🚀 Ready for Cloud-Native CI/CD

Migrating from Jenkins to OpenShift Pipelines is a strategic move toward a scalable and cloud-native DevOps ecosystem. With Tekton’s modular design and OpenShift’s robust platform, you’re set for faster, more reliable software delivery.

Need help with migration or pipeline design? HawkStack Technologies specializes in Red Hat and OpenShift consulting. Reach out for expert guidance! For more details www.hawkstack.com 

[codecraftshop]

Openshift build trigger using openshift webhooks - continuous integration with webhook triggers

Openshift build trigger using openshift webhooks – continuous integration with webhook triggers

#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration

Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat…

[opsmxspinnaker]

Spinnaker is a Continuous Delivery (CD) platform that was developed at Netflix where they used it to perform a high number of deployments ( 8000+/day). Later they made it available as an open-source tool. Previously enterprise release cycles used to be stretched for 7/8 months. But with the availability of the Spinnaker CD tool, enterprises have been able to shorten the release cycles from months to weeks to days (even multiple releases a day).

There are several other CD tools available in the market but what made Spinnaker so special?

Spinnaker Features:

Multicloud Deployments

It includes support of deployment to multiple cloud environments like Kubernetes (K8s), OpenShift, AWS, Azure, GCP, and so on. It abstracts the cloud environment to be worked on and managed easily.

Automated releases

Spinnaker allows you to create and configure CD pipelines that can be triggered manually or by some events. Thus the entire release process is automated end-to-end,  

Safe Deployments

With a  high number of release deployments, it is hard to know if some unwanted or bad release has been deployed into production which otherwise should have been failed. The built-in rollback mechanisms with Spinnaker allow you to test and quickly rollback a deployment and lets the application go back to its earlier state.

Maintain Visibility & Control

This feature in Spinnaker allows you to monitor your application across different cloud providers without needing you to log in to multiple accounts.

So Spinnaker is a foundational platform for Continuous Delivery (CD) that can be quite easily extended to match your deployment requirements.

Overview of Spinnaker’s Application Management & Deployment Pipelines Functionality

Spinnaker supports application management. In the Spinnaker UI, an application is represented as an inventory of all the infrastructure resources – clusters/server-groups, load balancers, firewalls, functions (even serverless functions) that are part of your application.

You can manage the same application deployed to different environments like AWS, GCP, Kubernetes, and so on from the Spinnaker UI itself. Spinnaker supports access control for multiple accounts. For e.g. users like dev or testers with permission can deploy to Dev or Stage environments, where as only the Ops people get to deploy the application into production. You can view and manage the different aspects of the application – like scaling the application, view health of different Kubernetes pods that are running, and see the performance and output of those pods.

Spinnaker pipelines let you have all your application’s infrastructure up and running. You can define your deployment workflow and configure your pipeline-as-a-code (JSON). It enables github-style operations.

Spinnaker pipelines allow you to configure:

Execution options– flexibility to run fully automatically or have manual interventions

Automated triggers– the capability to trigger your workflows through Jenkins jobs, webhooks, etc

Parameters– ability to define parameter which can be also accessed dynamically during pipeline execution

Notifications– to notify stakeholders about the status of pipeline execution

As part of the pipeline, you can configure and create automated triggers. These triggers can be fired based on events like a code check-in to the github repository or a new image being published to a Docker repository. You can have them scheduled to run at frequent intervals. You can pass different parameters to your pipeline so that you can use the same pipeline to deploy to different stages just by varying the parameters. You can set up notifications for integrations with different channels like slack or email.

After configuring the setup you can add different stages each of which is responsible for doing a different set of actions like calling a Jenkins job,  deploying to Kubernetes, and so on.  All these stages are first-class objects or actions that are built-in and that allows you to build a pretty complex pipeline. Spinnaker allows you to extend these pipelines easily and also do release management.

Once you run the Spinnaker pipeline you can monitor the deployment progress. You can view and troubleshoot if somethings go wrong such as Jenkins build failure. After a successful build, the build number is passed and tagged to the build image which is then used in subsequent stages to deploy that image.

You can see the results of deployment like what yaml got deployed. Spinnaker adds a lot of extra annotations to the yaml code so that it can manage the resources. As mentioned earlier, you can check all aspects (status of the deployment, the health of infrastructure, traffic, etc) of the associated application resources from the UI.

So we can summarize that Spinnaker displays the inventory of your application i.e. it shows all the infrastructure behind that application and it has pipelines for you to deploy that application in a continuous fashion.

Problems with other CD tools

Each organization is at a different maturity level for their release cycles. Today’s fast-paced business environment may mandate some of them to push code checked-in by developers to be deployed to production in a matter of hours if not minutes. So the questions that developers or DevOps managers ask themselves are:

What if I want to choose what features to promote to the next stage?

What if I want to plan and schedule a release?

What if I want different stakeholders (product managers/QA leads) to sign off (approve) before I promote?

For all the above use cases, Spinnaker is an ideal CD tool of choice as it does not require lots of custom scripting to orchestrate all these tasks.  Although, there are many solutions in the marketplace that can orchestrate the business processes associated with the software delivery they lack interoperability- the ability to integrate with existing tools in the ecosystem.

Can I include the steps to deploy the software also in the same tool?

Can the same tool be used by the developers, release managers, operations teams to promote the release?

The cost of delivery is pretty high when you have broken releases. Without end-to-end integration of delivery stages, the deployment process often results in broken releases. For e.g. raising a Jira ticket for one stage, letting custom scripting be done for that stage, and passing on to the next stage in a similar fashion.

Use BOM (bill-of-materials) to define what gets released

Integrate with your existing approval process in the delivery pipeline

Do the actual task of delivering the software

Say, your release manager decides that from ten releases, release A and B  (i.e. components of software) will be released. Then it needs all the approvals ( from testers/DevOps/Project managers/release manager) to be integrated into the deployment process of these releases. And, all this can be achieved using a Spinnaker pipeline.

Example of a Spinnaker pipeline

The BOM application configuration ( example below) is managed in some source control repository. Once you make any change and commit, it triggers the pipeline that would deploy the version of the services. Under the hood, Spinnaker would read the file from a repository, and inject it into the pipeline, deploy the different versions of the services, validate the deployment and promote it to the next stage.  

Example of a BOM

A BOM can have a list of services that have been installed. You may not install all services in the release or promote all the services. So you will declare if the service is being released or not, and the version of the release or image that is going to be published. Here in this example, we are doing it with a Kubernetes application.  You can also input different parameters that are going to be part of the release e.g. release it in the US region only.

So the key features of this release process are:

Source Controlled

Versioned (Know what got released and when?)

Approved (Being gated makes the release items become the source of truth. Once it is merged with the main branch it’s ready to get deployed)

Auditable ( Being source-controlled, it will definitely have the audit history about who made the change, and what changes were made)

Some interesting ways to enforce approvals

Integrations with Jira, ServiceNow

Policy checks for release conformance

Manual Judgment

Approvals would include integrations with Jira, ServiceNow, policy checks for release conformance e.g. before you release any release items you need to have their SonarQube coverage for static analysis of code quality and security vulnerabilities at 80%. Finally, if you are not ready to automatically promoting the release to production you can make a manual judgment and promote the same

Spinnaker supports managing releases giving you control over what version of different services would get deployed and released. So all the versions need not have continuous delivery but planned release. It lets you plan releases, determine what releases would get promoted, and promote them through the whole process in an automated manner.

OpsMx is a leading provider of Continuous Delivery solutions that help enterprises safely deliver software at scale and without any human intervention. We help engineering teams take the risk and manual effort out of releasing innovations at the speed of modern business.

[codecraftshop]

Openshift build trigger using openshift webhooks - continuous integration with webhook triggers#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat openshift,deploy openshift web application using openshift cli command line red hat openshift,web application openshift online,openshift container platform,kubernetes,red hat openshift,openshift 4,openshift tutorial,redhat openshift online,openshift for beginners,openshift login https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Openshift build trigger using openshift webhooks - continuous integration with webhook triggers | Openshift build trigger using openshift webhooks - using openshift pipelines with webhook triggers In this course we will learn about using openshift webhooks. We will deploy and configure a web based application to integrate with github. We will use openshift github webhooks and configure it in the github repository under Webhooks section. Then we will verify the webhooks whether openshift webhook is configured correctly or not. Then in the end we will commit change so that openshift build gets trigger whenever any commit happen in the git repo. Red Hat is the world's leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies. deploy jenkins on openshift origin - Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Openshift/ Openshift4 a cloud based container to build deploy test our application on cloud. In the next videos we will explore Openshift4 in detail. https://www.facebook.com/codecraftshop/ https://t.me/codecraftshop/ Please do like and subscribe to my you tube channel "CODECRAFTSHOP" Follow us on facebook | instagram | twitter at @CODECRAFTSHOP .

[codecraftshop]

Openshift build trigger using openshift webhooks - continuous integration with webhook triggers

Openshift build trigger using openshift webhooks – continuous integration with webhook triggers

#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration

Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat openshift,deploy openshift web application using openshift cli command…

[codecraftshop]

Openshift build trigger using openshift webhooks - continuous integration with webhook triggers#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat openshift,deploy openshift web application using openshift cli command line red hat openshift,web application openshift online,openshift container platform,kubernetes,red hat openshift,openshift 4,openshift tutorial,redhat openshift online,openshift for beginners,openshift login https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Openshift build trigger using openshift webhooks - continuous integration with webhook triggers | Openshift build trigger using openshift webhooks - using openshift pipelines with webhook triggers In this course we will learn about using openshift webhooks. We will deploy and configure a web based application to integrate with github. We will use openshift github webhooks and configure it in the github repository under Webhooks section. Then we will verify the webhooks whether openshift webhook is configured correctly or not. Then in the end we will commit change so that openshift build gets trigger whenever any commit happen in the git repo. Red Hat is the world's leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies. deploy jenkins on openshift origin - Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Openshift/ Openshift4 a cloud based container to build deploy test our application on cloud. In the next videos we will explore Openshift4 in detail. https://www.facebook.com/codecraftshop/ https://t.me/codecraftshop/ Please do like and subscribe to my you tube channel "CODECRAFTSHOP" Follow us on facebook | instagram | twitter at @CODECRAFTSHOP .

[codecraftshop]

Openshift build trigger using openshift webhooks - openshift webhook triggers

Openshift build trigger using openshift webhooks – openshift webhook triggers

#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration

Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat…

[codecraftshop]

Openshift build trigger using openshift webhooks - openshift webhook triggers#build #trigger #openshift #openshiftwebhooks #githubwebhooks #continuousintegration Openshift build trigger using openshift webhooks,openshift, using openshift pipelines with webhook triggers, continuous integration,containers,red hat,openshift openshift 4 red hat openshift container platform,openshift openshift 4 red hat openshift,deploy openshift web application using openshift cli command line red hat openshift,web application openshift online,openshift container platform,kubernetes,red hat openshift,openshift 4,openshift tutorial,redhat openshift online,openshift for beginners,openshift login https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Openshift build trigger using openshift webhooks - continuous integration with webhook triggers | Openshift build trigger using openshift webhooks - using openshift pipelines with webhook triggers In this course we will learn about using openshift webhooks. We will deploy and configure a web based application to integrate with github. We will use openshift github webhooks and configure it in the github repository under Webhooks section. Then we will verify the webhooks whether openshift webhook is configured correctly or not. Then in the end we will commit change so that openshift build gets trigger whenever any commit happen in the git repo. Red Hat is the world's leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies. deploy jenkins on openshift origin - Continuous Integration (CI) is a development practice that requires developers to integrate code into a shared repository several times a day. Openshift/ Openshift4 a cloud based container to build deploy test our application on cloud. In the next videos we will explore Openshift4 in detail. https://www.facebook.com/codecraftshop/ https://t.me/codecraftshop/ Please do like and subscribe to my you tube channel "CODECRAFTSHOP" Follow us on facebook | instagram | twitter at @CODECRAFTSHOP . docker

[codecraftshop]

Deploy Springboot mysql application on Openshift#openshift #openshift4 #springbootmysql #mysqlconnectivity #SpringbootApplicationWithMysql Deploy Springboot mysql application on Openshift,spring boot with mysql on k8s,openshift deploy spring boot jar,spring boot java with mysql on kubernetes,spring boot mysql kubernetes example,spring boot with mysql on kubernetes,deploy web application in openshift web console,how to deploy spring boot application to google app engine,deploying spring boot in kubernetes,how to deploy application on openshift,openshift deploy java application,openshift,spring boot,red hat https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Deploy Springboot mysql application on Openshift In this course we will learn about deploying springboot application with mysql database connectivity in openshift. Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment Experience with RedHat OpenShift 4 Container Platform. This course introduces OpenShift to an Absolute Beginner using really simple and easy to understand lectures. What is Openshift online and Openshift dedicated gives administrators a single place to implement and enforce policies across multiple teams, with a unified console across all Red Hat OpenShift clusters. Red Hat is the world's leading provider of enterprise open source solutions, including high-performing Linux, cloud, container, and Kubernetes technologies. you will learn how to develop build and deploy spring boot application with mysql on a kubernetes cluster and also you can learn how to create configmaps and secrets on a kubernetes cluster. building and deploying spring boot application with mysql on kubernetes cluster. Openshift/ Openshift4 a cloud based container to build deploy test our application on cloud. In the next videos we will explore Openshift4 in detail. Commands used in this video : 1. Source code location: https://github.com/codecraftshop/SpringbootOpenshitMysqlDemo.git 2. Expose the service command. oc expose svc/mysql oc describe svc/mysql Openshift related videos: Openshift : 1-Introduction to openshift and why openshift - introduction to openshift https://youtu.be/yeTOjwb7AYU Openshift : 2-Create openshift online account to access openshift cluster https://youtu.be/76N7RQfzm14 Openshift : 3-Introduction to openshift online cluster | overview of openshift online cluster https://youtu.be/od3qCzzIPa4 Openshift : 4-Login to openshift cluster in different ways | openshift 4 https://youtu.be/ZOAs7_1xFNA Openshift : 5-How to deploy web application in openshift web console https://youtu.be/vmDtEn_DN2A Openshift : 6-How to deploy web application in openshift command line https://youtu.be/R_lUJTdQLEg Openshift : 7-Deploy application in openshift using container images https://youtu.be/ii9dH69839o Openshift : 8-Deploy jenkins on openshift cluster - deploy jenkins on openshift | openshift https://youtu.be/976MEDGiPPQ Openshift : 9-Openshift build trigger using openshift webhooks - continuous integration with webhook triggers https://youtu.be/54_UtSDz4SE Openshift : 10-Install openshift 4 on laptop using redhat codeready containers - CRC https://youtu.be/9A05yTSjiFI https://www.facebook.com/codecraftshop/ https://t.me/codecraftshop/ Please do like and subscribe to my you tube channel "CODECRAFTSHOP" Follow us on facebook | instagram | twitter at @CODECRAFTSHOP .

[codecraftshop]

https://youtu.be/3OfS5QYo77M#openshiftpipelinesusingtekton #openshift4 #tektonpipelines #CICDpipelines #continuousintegration openshift pipelines using tekton,openshift pipelines using tektonan,openshift,installing openshift pipelines,openshift pipelines based on tekton,tekton,kubernetes,openshift pipelines using tektonic,openshift pipelines tutorial using tekton,ci cd pipelines in openshift,pipelines on red hat openshift,continuous integration,red hat,cli tekton pipelines operator,application using tektoncd pipelines,tekton-pipelines,cicd,cloud-native,containers,pipelines,tektoncd,pipeline https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Openshift pipelines using Tekton - Tekton pipelines with openshift In this course we will learn about OpenShift Pipelines are cloud-native, continuous integration and continuous delivery (CI/CD) solutions based on Kubernetes resources. It uses Tekton Pipelines to automate deployments across multiple platforms by abstracting away the underlying details. Tekton introduces a number of standard Custom Resource Definitions (CRDs) for defining pipelines that are portable across Kubernetes distributions. -Installing the Pipelines Operator in Web Console OpenShift Pipelines can be installed by using the operator listed in the OpenShift OperatorHub. When you install the pipelines operator, the custom resources required for the pipeline configuration are automatically installed along with the operator. -Installing the OpenShift Pipelines operator using the CLI You can install OpenShift Pipelines operator from the OperatorHub using the CLI. In the next videos we will explore Openshift4 in detail. Openshift related videos: Openshift : 1-Introduction to openshift and why openshift - introduction to openshift https://youtu.be/yeTOjwb7AYU Openshift : 2-Create openshift online account to access openshift cluster https://youtu.be/76N7RQfzm14 Openshift : 3-Introduction to openshift online cluster | overview of openshift online cluster https://youtu.be/od3qCzzIPa4 Openshift : 4-Login to openshift cluster in different ways | openshift 4 https://youtu.be/ZOAs7_1xFNA Openshift : 5-How to deploy web application in openshift web console https://youtu.be/vmDtEn_DN2A Openshift : 6-How to deploy web application in openshift command line https://youtu.be/R_lUJTdQLEg Openshift : 7-Deploy application in openshift using container images https://youtu.be/ii9dH69839o Openshift : 8-Deploy jenkins on openshift cluster - deploy jenkins on openshift | openshift https://youtu.be/976MEDGiPPQ Openshift : 9-Openshift build trigger using openshift webhooks - continuous integration with webhook triggers https://youtu.be/54_UtSDz4SE Openshift : 10-Install openshift 4 on laptop using redhat codeready containers - CRC https://youtu.be/9A05yTSjiFI Openshift : 11-Openshift pipelines using Tekton - Tekton pipelines with openshift https://youtu.be/3OfS5QYo77M https://www.facebook.com/codecraftshop/ https://t.me/codecraftshop/ Please do like and subscribe to my you tube channel "CODECRAFTSHOP" Follow us on

[codecraftshop]

Install openshift 4 on laptop using redhat codeready containers - CRC#openshift4 #openshift4onlaptop #codereadycontainers #redhat #localKubernetes Install openshift 4 on laptop,openshift 4 on laptop,openshift 4 on your laptop,install openshift 4 on laptop using redhat,Install openshift 4 on laptop using redhat codeready containers,openshift,red hat,kubernetes,OpenShift development,Kubernetes Development,Kubernetes development,Local kubernetes,codeready,codeready containers,cicd,paas,openshift 4,openshift openshift 4 red hat openshift,openshift container platform,redhat openshift online,red hat openshift https://www.youtube.com/channel/UCnIp4tLcBJ0XbtKbE2ITrwA?sub_confirmation=1&app=desktop About: 00:00 Install openshift 4 on laptop using redhat codeready containers- CRC In this course we will learn about openshift 4 on your laptop - Red Hat OpenShift 4 Container Platform: Download OpenShift 4 client (self) Red Hat OpenShift 4 on your laptop: Introducing Red Hat CodeReady Containers RedHat Openshift Online Platform Red Hat OpenShift is an open source container application platform based on the Kubernetes container orchestrator for enterprise application development and deployment Experience with RedHat OpenShift 4 Container Platform. In the next videos we will explore Openshift4 in detail. Openshift related videos: Openshift : 1-Introduction to openshift and why openshift - introduction to openshift https://youtu.be/yeTOjwb7AYU Openshift : 2-Create openshift online account to access openshift cluster https://youtu.be/76N7RQfzm14 Openshift : 3-Introduction to openshift online cluster | overview of openshift online cluster https://youtu.be/od3qCzzIPa4 Openshift : 4-Login to openshift cluster in different ways | openshift 4 https://youtu.be/ZOAs7_1xFNA Openshift : 5-How to deploy web application in openshift web console https://youtu.be/vmDtEn_DN2A Openshift : 6-How to deploy web application in openshift command line https://youtu.be/R_lUJTdQLEg Openshift : 7-Deploy application in openshift using container images https://youtu.be/ii9dH69839o Openshift : 8-Deploy jenkins on openshift cluster - deploy jenkins on openshift | openshift https://youtu.be/976MEDGiPPQ Openshift : 9-Openshift build trigger using openshift webhooks - continuous integration with webhook triggers https://youtu.be/54_UtSDz4SE Openshift : 10-Install openshift 4 on laptop using redhat codeready containers - CRC https://youtu.be/9A05yTSjiFI Hyper-V related videos: Hyper-V : 1-Introduction to hyper v on windows 10 | Introduction to hyper-v on windows 10 https://youtu.be/aMYsjaPVswg Hyper-V : 2-Install hyperv on windows 10 - how to install hyper-v on windows 10 https://youtu.be/KooTCqf07wk Hyper-V : 3-Create a virtual machine with hyper-v manager on windows 10 https://youtu.be/pw_ETlpqqQk Hyper-V : 4-Create virtual switch in hyper v - creating virtual switch and virtual networks in hyper v https://youtu.be/5ERXyGiXqu4 Hyper-V : 5-Customize virtual machine hyper v | hyper-v virtual machine customization https://youtu.be/xLFHhgtPymY Hyper-V : 6-Install ubuntu 20.04 on windows 10 using hyper v virtual machine https://youtu.be/ch_bXvet9Ys STS 4 related videos: Spring Tool Suite 4 : 1-STS4 - Getting Started with Spring Tools S