-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: add inst for preinstalled (#83)
- Loading branch information
1 parent
88039a8
commit a4e89fd
Showing
9 changed files
with
163 additions
and
36 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,17 +1,130 @@ | ||
| --- | ||
| slug: akamai-cloud | ||
| title: Akamai Connected Cloud | ||
| sidebar_label: Akamai Cloud | ||
| sidebar_label: Akamai Connected Cloud | ||
| --- | ||
|
|
||
| ## Comming soon! | ||
| :::info | ||
| Coming soon! | ||
| ::: | ||
|
|
||
| Soon you'll be able to provision a LKE cluster combined with the Application Platform. This will have the following advantages compared to installing the Application Platform manually: | ||
| ## Create an LKE cluster | ||
|
|
||
| - The Application Platform will be automatically installed for you on LKE. | ||
| 1. Log into your Cloud Manager account. | ||
|
|
||
| - Each LKE cluster where the Application Platform is installed will automatically be configured to use Akamai Edge DNS (for FREE!). | ||
| 2. Select Kubernetes from the left navigation menu and then click Create Cluster. | ||
|
|
||
| - If approved by the user, all the required Buckets in Object Storage will be automatically created in your account. | ||
|
|
||
| Like to be the first to try it out? Sign up now for the [Beta Program](https://cloud.linode.com/betas)! | ||
| 3. The Create a Kubernetes Cluster page appears. At the top of the page, you are required to select the following options | ||
|
|
||
|
|
||
| - In the Cluster Label field, provide a name for your cluster. The name must be unique between all of the clusters on your account. This name is how you identify your cluster in Cloud Manager’s Dashboard. | ||
|
|
||
|
|
||
| - From the Region dropdown menu, select the Region where you would like your cluster to reside. | ||
|
|
||
|
|
||
| - From the Version dropdown menu, select a Kubernetes version to deploy to your cluster. | ||
|
|
||
|
|
||
| 4. In the Application Platform for LKE section, select “Yes, enable Application Platform for LKE” | ||
|
|
||
| :::note | ||
| The Application Platform for LKE requires HA control plane to be enabled. When Application Platform for LKE is enabled, HA control plane will automatically be enabled. | ||
| ::: | ||
|
|
||
| 5. In the Add Node Pools section, select the hardware resources for the Linode worker node(s) that make up your LKE cluster. To the right of each plan, select the plus + and minus - to add or remove a Linode to a node pool one at time. | ||
|
|
||
| :::note | ||
| The Application Platform for LKE requires a node pool with at least 3 worker nodes with a total minimum of 16 GB memory and 12 CPUs. Linode plans that do not provide the minimal required resources can not be selected. | ||
| ::: | ||
|
|
||
| 6. Select Add to include the node pool in your configuration. If you decide that you need more hardware resources after you deploy your cluster, you can always [edit your Node Pool](https://techdocs.akamai.com/cloud-computing/docs/manage-nodes-and-node-pools). | ||
|
|
||
| 7. Once a pool has been added to your configuration, it is listed in the Cluster Summary on the right-hand side of Cloud Manager detailing your cluster's hardware resources and monthly cost. Additional pools can be added before finalizing the cluster creation process by repeating the previous step for each additional pool. | ||
|
|
||
| 8. When you are satisfied with the configuration of your cluster, click the Create Cluster button on the right hand side of the screen. Your cluster's detail page appears, and your Node Pools are listed on this page. First the LKE cluster will be created and once ready the Application Platform for LKE will be installed. The installation of the Application Platform for LKE takes around 10 until 15 minutes. When the installation is finished, the URL of the Portal Endpoint will appear in the Application Platform for LKE section. The progress of the installation will be checked every 60 seconds. When the installation is still in progress, the URL of the Portal Endpoint will not be displayed. Instead the message “Installation in progress” will appear. | ||
|
|
||
|
|
||
| 9. When the installation of both the LKE cluster and the Application Platform is ready, click on the provided URL of the portal Endpoint. You will then see the following sign-in page: | ||
|
|
||
| 10. Continue with the next steps to get the initial credentials needed to sign in. | ||
|
|
||
| ## Access and download your Kubeconfig | ||
|
|
||
| 1. To access your cluster's Kubeconfig, log in to your Cloud Manager account and navigate to the Kubernetes section. | ||
|
|
||
| 2. From the Kubernetes listing page, click on your cluster's more options ellipsis and select Download Kubeconfig. The file is saved to your computer's Downloads folder. | ||
|
|
||
| 3. Open a terminal shell and save your Kubeconfig file's path to the $KUBECONFIG environment variable. In the example command, the Kubeconfig file is located in the Downloads folder, but you should alter this line with this folder's location on your computer: | ||
|
|
||
| ```bash | ||
| export KUBECONFIG=~/Downloads/kubeconfig.yaml | ||
| ``` | ||
|
|
||
| ## Obtain the initial access credentials and sign in | ||
|
|
||
| 1. Perform the following command to obtain the user name: | ||
|
|
||
| ```bash | ||
| kubectl get secret platform-admin-initial-credentials -n keycloak --template={{.data.username}} | base64 -d | ||
| ``` | ||
|
|
||
| 2. Perform the following command to obtain the initial password: | ||
|
|
||
| ```bash | ||
| kubectl get secret platform-admin-initial-credentials -n keycloak --template={{.data.password}} | base64 -d | ||
| ``` | ||
|
|
||
| 3. Copy the username and password to your clipboard. | ||
|
|
||
| 4. Sign in to the Console with the provided username and initial password. | ||
|
|
||
| 5. Change the initial password | ||
|
|
||
| ## Provision Object Storage for the Application Platform | ||
|
|
||
| When signed in to the Console (the web UI of the Application Platform), the first thing you’ll need to do is configure Object Storage. A wizard will be displayed asking you if the Application Platform should provision all the required Buckets and access key for you. This is not required, but strongly recommended as this will prevent `out of disk space errors` when using Storage Volumes for integrated applications. Using Object Storage also has the advantage to create backups of all databases used by the platform. | ||
|
|
||
| 1. When asked to create all the required Buckets and access key, click Yes. If you don’t want the platform to create all the required buckets, then click Skip. Note that in this case some features like creating backups of databases will not be available. You can start the Wizard at any time in the Console (Platform View: Maintenance, Show Object Storage Wizard). | ||
|
|
||
| 2. Follow the instructions to [create a Personal Access Token](https://techdocs.akamai.com/linode-api/reference/get-started#personal-access-tokens) and make sure to select **Read/Write** for the Object Storage category and **Read** for the Kubernetes category. Copy the Access Token. | ||
|
|
||
| 3. Now paste the Access Token into the wizard and click Submit. | ||
|
|
||
| All the required Buckets and Access Key will now be created in your account and the platform will be configured to use Object Storage to store persistent data and backups. The provided Personal Access Token will not be stored. The created buckets will have the `<cluster-id>` prefix` | ||
|
|
||
| ## Known issues | ||
|
|
||
| If the URL of the Portal Endpoint does not appear in the Application Platform for LKE section after 30 minutes, then the following may be the issue: | ||
|
|
||
| ### Installation gets stuck because of a quota exceeded exception | ||
|
|
||
| Next to the resources required for LKE, the Application Platform also uses a NodeBalancer and a minimum of 11 Storage Volumes. This might result in a quota exceeding exception. Linode currently does not provide quota limits in your account details at this time. | ||
|
|
||
| The following issue might be related to quota exceeding exception: | ||
|
|
||
| Pods that require a Storage Volume get stuck in a pending state with the following message: | ||
|
|
||
| `pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.` | ||
|
|
||
| Resolution: | ||
|
|
||
| - Remove any Storage Volumes that are Unattached. | ||
|
|
||
| - If you would like to know your account's limits or want to increase the number of entities you can create, the best way is to get that information through a support ticket. | ||
|
|
||
| ### The Let’s Encrypt secret request was not successful | ||
| For each cluster with the Application Platform for LKE enabled, a Let’s Encrypt certificate will be requested. If the certificate is not ready within 30 minutes, the installation of the Application Platform will fail. Run the following command to see if the certificate is created: | ||
|
|
||
| ```bash | ||
| kubectl get secret -n istio-system | ||
| ``` | ||
|
|
||
| There should be a secret called: `apl-<cluster-id>-wildcard-cert` | ||
|
|
||
| If this secret is not present, then the request failed. | ||
|
|
||
| Resolution: | ||
|
|
||
| - Delete the LKE cluster with Application Platform for LKE enabled and create a new cluster with Application Platform for LKE enabled |