ENDOC-466 Azure install 7.0 update, first draft #474
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jyunmitch
commented
Apr 13, 2022
| If you're already comfortable setting up an AKS cluster and installing NGINX, then you may be able to skip to [setting up Entando](#install-the-entando-custom-resource-definitions). | ||
| - Azure account | ||
| - **Note:** If you're using an Azure free account, you may need to upgrade your account to enable pay-as-you-go billing. The Azure free account default quota allows just 1-4 vCPU which is not sufficient for this tutorial. There may be a delay before the quotas are updated when you upgrade your account. | ||
| - If you choose not to use the Azure Cloud Shell, you'll also need the Azure command line tool |
There was a problem hiding this comment.
period at end of sentence
| 15. Click `Next: Networking` | ||
| 16. Keep the default settings | ||
| 17. Click `Review + Create` | ||
| - Note: There are many other configuration options available for an AKS cluster. Generally, you can change these based on your experience and comfort level with the platform. Entando uses base Kubernetes APIs so as long as you follow the Entando configuration instructions below you can tune your cluster infrastructure to meet your goals. |
There was a problem hiding this comment.
added commas >> Entando uses base Kubernetes APIs, so as long as you follow the Entando configuration instructions below, you can tune...
| 4. Now create the ConfigMap for the operator | ||
| ``` sh | ||
| kubectl apply -f sample-configmaps/entando-operator-config.yaml -n entando | ||
| 2. Edit `entando-app.yaml`. Replace `YOUR-HOST-NAME` with `EXTERNAL-IP + .nip.io`. See [this page](../../docs/consume/custom-resources.md#entandoapp) for details on other `EntandoApp` options. |
There was a problem hiding this comment.
See [this page] >> See the [custom resources page]
| ``` | ||
|
|
||
| Double check your availability zones. By default an Azure cluster will include nodes from multiple zones, but Azure may not automatically provision their storage. | ||
| If you get an error like: `0/5 nodes are available: 5 node(s) had volume node affinity conflict` or if several deployments fail to start, then you should check your availability zones. By default an Azure cluster will include nodes from multiple zones, but Azure may not automatically provision their storage. |
There was a problem hiding this comment.
By default an Azure cluster>> By default, an Azure cluster
Lyd1aCla1r3
reviewed
Apr 14, 2022
|
|
||
| ### Install the Entando Custom Resources | ||
|
|
||
| 1. Apply the cluster-scoped Custom Resource Definitions (CRDs). This is required only once per cluster. |
There was a problem hiding this comment.
custom resource definitions ??
|
|
||
| ### Deploy NGINX Ingress Controller | ||
|
|
||
| 1. Navigate to your cluster by clicking `Go to Resource` from the results page or by the top navigation `Home - Kubernetes service` and clicking on your cluster. | ||
| 1. Navigate to your cluster by clicking `Go to Resource` from the results page, or the breadcrumb navigation `Home` → `Kubernetes service` and clicking on your cluster. |
There was a problem hiding this comment.
or use the breadcrumb...and click (reads a little better)
| - If you're not using Azure Cloud Shell, you'll also need: | ||
| - Azure command line tool | ||
| - Helm3 client | ||
| The steps below walk you through installing the Entando Platform in an Azure Kubernetes Services (AKS) cluster. This is the process. |
There was a problem hiding this comment.
is "This is the process" needed?
|
|
||
| If you're already comfortable setting up an AKS cluster and installing NGINX, then you may be able to skip to [setting up Entando](#install-the-entando-custom-resource-definitions). | ||
| - Azure account | ||
| - **Note:** If you're using an Azure free account, you may need to upgrade your account to enable pay-as-you-go billing. The Azure free account default quota allows just 1-4 vCPU which is not sufficient for this tutorial. There may be a delay before the quotas are updated when you upgrade your account. |
There was a problem hiding this comment.
Note: vs Note: vs > Note vs tip :(
| ## Deploy Your Entando Application | ||
| You can now deploy your application to Azure Kubernetes Service. | ||
| 1. Download and unpack the entando-helm-quickstart files | ||
| 6. Apply the namespace-scoped Custom Resources |
| 3. Click on the deployment name inside that application. There will be one | ||
| 1. In your cluster, select `Workloads` in the left nav | ||
| 2. Click on the deployment for your server application. This is `quickstart-deployment` by default. | ||
| 3. Click on the deployment name inside that application. There will be one. |
There was a problem hiding this comment.
"There will be one" ? like a single one or it will exist?
| 4. Click on the tab labeled `Conditions` | ||
| 5. If you see an error that says `0/5 nodes are available: 5 node(s) had volume node affinity conflict.` Then you need to reconfigure | ||
| your cluster to have nodes in one zone or work with your Azure operations team to provision storage to match node affinity. | ||
| 5. If you see an error that says `0/5 nodes are available: 5 node(s) had volume node affinity conflict.` You need to reconfigure your cluster to have nodes in one zone or work with your Azure operations team to provision storage to match node affinity. |
There was a problem hiding this comment.
"if" needs a "then"
period outside of message (is currently inside the backtick)
nshaw
approved these changes
Apr 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the troubleshooting section at the bottom, there is a list of pods that looks wrong. I've listed the new ones below so you can check that these are the correct ones to use, but the status for each pod may be wrong for the error they are talking about.