This micro learning is a continuation of installing the quickstart environment with ENT CLI. In this lesson, we’ll take a deeper look at what gets installed.
This micro learning series will help you get familiar with Entando CLI (ENT) which simplifies building and deploying applications for Kubernetes.
This is a continuation of installing the quickstart environment with ENT CLI. In this lesson, we’ll take a deeper look at what gets installed. It covers:
Previously, we passed in a number of arguments and options in the quickstart command. Let’s take a brief look at each one.
ent quickstart "entando" "quickstart" --simple --release="v6.3.2" --debug=1 --with-vm --yes
These are the important items to note. The Kubernetes namespace, the name of your application, --simple, --release, and --with-vm.
|"entando" (Argument #1)||The Kubernetes namespace where we’ll install Entando.|
|"quickstart" (Argument #2)||The name of your Entando application.|
Performs a standard install.
Alternative installation options include:
The tag of the Entando release we want to use.
|--debug=1||Displays debug information.|
|--with-vm||Installs Entando inside a VM.|
|--yes||Assumes “yes” for all prompts.|
Here’s an outline of what gets installed by ENT CLI.
|Linux VM||Creates an Ubuntu VM (entando) using Multipass.|
|Entando CLI||Installs an instance of ENT CLI inside the VM.|
|Kubernetes||Installs k3s, a lightweight distribution of Kubernetes.|
Downloads the specified Entando release.
Generates Entando Helm deployment.
In your Linux VM created by ENT CLI, see:
The Helm deployment (entando-deployment-specs.yaml) specifies the images that are downloaded when deploying Entando to Kubernetes.
|Entando App Builder||
The administrative interface for building and designing applications.
|Entando App Engine||
|Entando Component Repository||
Private repository where you can share and install frontend and backend components for one or more Entando applications.
|Entando Cluster Infrastructure||
A wrapper used by Entando App Engine to call Kubernetes services.
|Entando Identity Management||
Centralized authentication for individual micro frontends, microservices, and the entire application for one or more Entando applications.
|Run to Completion Jobs||
Jobs that are run once to install and configure:
Entando App Engine
Entando Cluster Infrastructure
Entando Identity Management
Next, Kubernetes adds the custom resource definitions that will be used to install and configure the Entando application.
Developers can choose to build one or more Entando applications (EntandoApp).
An EntandoApp consists of 3 images:
Links an EntandoPlugin to an EntandoApp.See: EntandoPlugin
|EntandoClusterInfrastructure||Shared cluster services used by one or multiple Entando applications (EntandoApp). Used to access Kubernetes services.|
Packages the components (or custom resources) that make up an Entando application, and deploys them in sequential order.
Not to be confused with EntandoApp which represents an Entando application instance and can be configured to reuse shared resources like EntandoClusterInfrastructure and EntandoKeycloakServer.
|EntandoDatabaseService||Installs database services. Can be configured to connect to an existing database service.|
Deploys and configures a Red Hat Keycloak Server instance on the cluster.
Not required if you’d like to use an existing Keycloak server for identity management.
A Spring Boot microservice that can be made available to an Entando application.
Creates an ingress path for the microservice.
Check out the docs for code examples and properties you can use to tailor each custom resource for your environment.
Ingresses (or routes) from which you can access Entando services from outside the cluster.
|Entando App Builder||/app-builder/|
|Entando App Engine||
*Can be configured for a given Entando application.
|Entando Component Repository||/digital-exchange|
|Entando Cluster Infrastructure||/k8s|
|Entando Identity Management||/auth|
The Entando Operator listens for events with Entando custom resources and will create persistent volumes if storageClass is specified for that custom resource. The operator will use the default storage class for the cluster by default.
Stores images, documents, and any static assets uploaded to the CMS.
Stores files uploaded to the server.
Persistent storage for the selected database management system (DBMS).
A given microservice deployed via an Entando Plugin can optionally request persistent storage for storing and retrieving files.
In the next lesson, we’ll learn how ENT CLI makes it easy to package and deploy frontend and backend code changes to your application in Kubernetes.
Entando is the leading modular application platform for building enterprise web apps on Kubernetes.
Our platform integrates trusted open source technologies and extends their functionality to give you a cohesive and streamlined developer experience with easy-to-use patterns. From deploying on Kubernetes to creating modular backend and frontend architectures using your current technologies, Entando helps you at every layer of the stack.
Entando is open source with available enterprise support and services. Begin developing on the platform today, and get a quote to see how our team can help your enterprise build better apps, sites, and portals--faster.