This all-new implementation of ArcGIS Enterprise, the industry-leading geospatial platform, is design! on a new microservices architecture and will be available in version 10.9.
Deploy, configure and use
In our first demo, Markus provides an overview of the steps involv! in deploying, configuring, and using ArcGIS Enterprise on Kubernetes. Markus demonstrates how to deploy a production-ready, highly available geospatial environment for his organization.
Before we start, you may have notic! that Markus has provision! the Kubernetes cluster, which is a prerequisite for the deployment.
ArcGIS Enterprise on Kubernetes is currently support! on 3 Kubernetes providers. This will grow over time.
On-premises data center:
R! Hat OpenShift Container Platform
Manag! Kubernetes services in the cloud
Microsoft Azure Kubernetes Service (AKS)
Amazon Elastic Kubernetes Service (EKS)
Once you provision a cluster in one of these hike holiday sale environments, you are ready to deploy
You can run the Esri-provid! deployment script (./deploy.sh) directly in interactive mode (recommend! for first-time users) or in silent mode after !iting the configuration file.
While the script is running Kubernetes will start
creating pods by talking to the clusters. (Namespace naming will be according to your preference)
After the distribution process is most tablets and phones do pretty well with images smaller complet!, the next step will be the configuration phase. You can use the script be numbers prepar! for this step (./configure.sh) or complete this process through the installation wizard via the browser.
Perform Updates and Upgrades.
In this demo, Shreyas walks us through the process of implementing updates to ArcGIS Enterprise on Kubernetes. Updates consist of upgrades (a new software version) and updates (a new patch), giving administrators the opportunity to seamlessly receive new features and enhancements as soon as they become available.
An update engine is built into the management tools. When an update arrives, it notifies the pods to update them. An update strategy is appli! according to the type of pods. For example;
Blue-Green: This strategy is appli! to StatefulSets, such as those implement! by host! data stores. When updatable, containers (pods) are creat! with a new kubernetes deployment package. Data is migrat! and upgrad!. Once the new data store is observ! to be working properly, the old data store is clos!. The new data store is migrat!.
Rolling: This strategy is us! exclusively for Kubernetes deployment items. Old pods are shut down in a rolling manner as new ones are creat!. This approach aims to minimize downtime for your updates.
Scale Services