diff --git a/docs/get-started/installation/akamai-cloud.md b/docs/get-started/installation/akamai-connected-cloud.md similarity index 90% rename from docs/get-started/installation/akamai-cloud.md rename to docs/get-started/installation/akamai-connected-cloud.md index 3177abe1e..41db1e195 100644 --- a/docs/get-started/installation/akamai-cloud.md +++ b/docs/get-started/installation/akamai-connected-cloud.md @@ -1,32 +1,25 @@ --- -slug: akamai-cloud +slug: akamai-connected-cloud title: Akamai Connected Cloud sidebar_label: Akamai Connected Cloud --- -:::info -Coming soon! -::: +# Get started with the Application Platform for LKE -## Create an LKE cluster +## Create a Kubernetes cluster with the App Platform for LKE 1. Log into your Cloud Manager account. 2. Select Kubernetes from the left navigation menu and then click Create Cluster. - 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 @@ -39,14 +32,23 @@ The Application Platform for LKE requires HA control plane to be enabled. When A 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. ::: +:::note +The App Platform for LKE is not supported in combination with Shared CPU. +::: + 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: + +![details-page](../../img/cluster-details-page.png) -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: +You will then see the following sign-in page: + +![sign-in](../../img/sign-in-page.png) 10. Continue with the next steps to get the initial credentials needed to sign in. @@ -94,6 +96,11 @@ When signed in to the Console (the web UI of the Application Platform), the firs 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 `` prefix` +## Onboard Teams and Users +You can now start enabling Applications, onboarding [Teams](../../for-ops/console/teams) and create [Users](../../for-ops/console/user-management). + +We recommend to go through the [Hands-on Labs](../labs/overview) to learn how to take advantage of the Application Platform for LKE. + ## 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: diff --git a/docs/get-started/installation/overview.md b/docs/get-started/installation/overview.md index 21ad3fb95..dd2ec30cb 100644 --- a/docs/get-started/installation/overview.md +++ b/docs/get-started/installation/overview.md @@ -11,7 +11,7 @@ sidebar_label: Overview ### [Linode Kubernetes Engine (LKE)](linode.md) Create a LKE cluster and manually install the Application Platform. -### [Akamai Connected Cloud - Comming soon!](akamai-cloud.md) +### [Akamai Connected Cloud - Comming soon!](akamai-connected-cloud.md) Provision LKE with the Application Platform in Akamai Connected Cloud. ### [Custom](custom.md) diff --git a/docs/get-started/installation/post-install-steps.md b/docs/get-started/installation/post-install-steps.md index c43693227..ece4bece5 100644 --- a/docs/get-started/installation/post-install-steps.md +++ b/docs/get-started/installation/post-install-steps.md @@ -24,8 +24,8 @@ At the end of the logs you should see the following message: # The Application Platform console is available at https://console.${domainSuffix} # # Obtain login credentials by using the below commands: -# kubectl get secret platform-admin -n keycloak -o jsonpath='{.data.username}' | base64 -d -# kubectl get secret platform-admin -n keycloak -o jsonpath='{.data.password}' | base64 -d +# kubectl get secret platform-admin-initial-credentials -n keycloak -o jsonpath='{.data.username}' | base64 -d +# kubectl get secret platform-admin-initial-credentials -n keycloak -o jsonpath='{.data.password}' | base64 -d # ######################################################################################################################################## ``` diff --git a/docs/img/cluster-details-page.png b/docs/img/cluster-details-page.png new file mode 100644 index 000000000..7fd421542 Binary files /dev/null and b/docs/img/cluster-details-page.png differ diff --git a/docs/img/sign-in-page.png b/docs/img/sign-in-page.png new file mode 100644 index 000000000..b137d82b6 Binary files /dev/null and b/docs/img/sign-in-page.png differ diff --git a/sidebar-docs.js b/sidebar-docs.js index 1886688ed..62c36d4ec 100644 --- a/sidebar-docs.js +++ b/sidebar-docs.js @@ -8,7 +8,7 @@ module.exports = { { Installation: [ "get-started/installation/overview", - "get-started/installation/akamai-cloud", + "get-started/installation/akamai-connected-cloud", "get-started/installation/linode", "get-started/installation/custom", "get-started/installation/helm", diff --git a/src/pages/docs/get-started/index.tsx b/src/pages/docs/get-started/index.tsx index 786c442b6..e934af785 100644 --- a/src/pages/docs/get-started/index.tsx +++ b/src/pages/docs/get-started/index.tsx @@ -2,5 +2,5 @@ import React from "react"; import { Redirect } from "@docusaurus/router"; export default function Home() { - return ; + return ; } diff --git a/src/pages/docs/index.tsx b/src/pages/docs/index.tsx index 786c442b6..e934af785 100644 --- a/src/pages/docs/index.tsx +++ b/src/pages/docs/index.tsx @@ -2,5 +2,5 @@ import React from "react"; import { Redirect } from "@docusaurus/router"; export default function Home() { - return ; + return ; } diff --git a/src/pages/index.tsx b/src/pages/index.tsx index 786c442b6..e934af785 100644 --- a/src/pages/index.tsx +++ b/src/pages/index.tsx @@ -2,5 +2,5 @@ import React from "react"; import { Redirect } from "@docusaurus/router"; export default function Home() { - return ; + return ; }