You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -94,7 +94,7 @@ Sign into the App Platform web UI using the `platform-admin` account, or another
94
94
95
95
### Create a New Team
96
96
97
-
[Teams](https://apl-docs.net/docs/for-ops/console/teams) are isolated tenants on the platform to support Development/DevOps teams, projects or even DTAP. A Team gets access to the Console, including access to self-service features and all shared apps available on the platform.
97
+
[Teams](https://techdocs.akamai.com/app-platform/docs/platform-teams) are isolated tenants on the platform to support Development/DevOps teams, projects or even DTAP. A Team gets access to the Console, including access to self-service features and all shared apps available on the platform.
98
98
99
99
1. Select **view** > **platform**.
100
100
@@ -150,7 +150,7 @@ The [NVIDIA GPU Operator](https://docs.nvidia.com/datacenter/cloud-native/gpu-op
150
150
151
151
### Create a Workload for the kserve-crd Helm Chart
152
152
153
-
A [Workload](https://apl-docs.net/docs/for-devs/console/workloads) is a self-service feature for creating Kubernetes resources using Helm charts from the Catalog.
153
+
A [Workload](https://techdocs.akamai.com/app-platform/docs/team-workloads) is a self-service feature for creating Kubernetes resources using Helm charts from the Catalog.
154
154
155
155
1. Select **view**>**team** and **team**>**admin**in the top bar.
156
156
@@ -274,7 +274,7 @@ If you haven't done it already, request access to the Llama 3 LLM model. To do t
274
274
275
275
### Create a Sealed Secret
276
276
277
-
[Sealed Secrets](https://apl-docs.net/docs/for-devs/console/secrets) are encrypted Kubernetes Secrets stored in the Values Git repository. When a Sealed Secret is created in the Console, the Kubernetes Secret will appear in the Team's namespace.
277
+
[Sealed Secrets](https://techdocs.akamai.com/app-platform/docs/team-secrets) are encrypted Kubernetes Secrets stored in the Values Git repository. When a Sealed Secret is created in the Console, the Kubernetes Secret will appear in the Team's namespace.
278
278
279
279
1. Select **view** > **team** and **team** > **demo** in the top bar.
@@ -214,7 +214,7 @@ Make another Sealed Secret named `mysql-credentials` to establish root user cred
214
214
215
215
### Create a Network Policy
216
216
217
-
Create a [**Network Policy**](https://apl-docs.net/docs/for-ops/console/netpols) in the Team where the `kubeflow-pipelines` Helm chart will be installed (Team name **demo** in this guide). This allows communication between all Kubeflow Pipelines Pods.
217
+
Create a [**Network Policy**](https://techdocs.akamai.com/app-platform/docs/team-network-policies) in the Team where the `kubeflow-pipelines` Helm chart will be installed (Team name **demo** in this guide). This allows communication between all Kubeflow Pipelines Pods.
218
218
219
219
1. Select **view** > **team** and **team** > **demo** in the top bar.
@@ -99,7 +99,7 @@ Once your LKE cluster with App Platform has been fully deployed, [sign in](https
99
99
100
100
### Create a New Team
101
101
102
-
[Teams](https://apl-docs.net/docs/for-ops/console/teams) are isolated tenants on the platform to support Development and DevOps teams, projects, or even DTAP (Development, Testing, Acceptance, Production). A Team gets access to the Console, including access to self-service features and all shared apps available on the platform.
102
+
[Teams](https://techdocs.akamai.com/app-platform/docs/platform-teams) are isolated tenants on the platform to support Development and DevOps teams, projects, or even DTAP (Development, Testing, Acceptance, Production). A Team gets access to the Console, including access to self-service features and all shared apps available on the platform.
103
103
104
104
When working in the context of an admin-level Team, users can create and access resources in any namespace. When working in the context of a non-admin Team, users can only create and access resources used in that Team's namespace.
105
105
@@ -113,7 +113,7 @@ When working in the context of an admin-level Team, users can create and access
113
113
114
114
### Create a RabbitMQ Cluster with Workloads
115
115
116
-
A [Workload](https://apl-docs.net/docs/for-devs/console/workloads) is a self-service feature for creating Kubernetes resources using Helm charts from the Catalog.
116
+
A [Workload](https://techdocs.akamai.com/app-platform/docs/team-workloads) is a self-service feature for creating Kubernetes resources using Helm charts from the Catalog.
117
117
118
118
1. Switch to your newly created team view by selecting **view** > **team** and **team** > **demo** in the top bar. You can switch back to team `admin` as needed by selecting **view** > **team** and **team** > **admin**.
119
119
@@ -240,7 +240,7 @@ Once successfully built, copy the image repository link so that you can create a
240
240
241
241
In order for the RabbitMQ Cluster to be accessible, a Network Policy must be created.
242
242
243
-
A [Network Policy](https://apl-docs.net/docs/for-devs/console/netpols) in App Platform is a self-service method of controlling traffic to and from your deployment. Ingress (inbound) policies control access to internal Team pods, and egress (outbound) policies control traffic to external endpoints.
243
+
A [Network Policy](https://techdocs.akamai.com/app-platform/docs/team-network-policies) in App Platform is a self-service method of controlling traffic to and from your deployment. Ingress (inbound) policies control access to internal Team pods, and egress (outbound) policies control traffic to external endpoints.
244
244
245
245
1. Select **Network Policies** from the left menu, and click **Create NetPol**.
@@ -56,7 +57,7 @@ Sign into the App Platform web UI using the `platform-admin` account, or another
56
57
57
58
### Create a New Team
58
59
59
-
[Teams](https://apl-docs.net/docs/for-ops/console/teams) are isolated tenants on the platform to support Development/DevOps teams, projects, and methodologies, like [DTAP](https://en.wikipedia.org/wiki/Development,_testing,_acceptance_and_production). A Team gets access to the Console, which provides access to self-service features and the shared apps available on the platform.
60
+
[Teams](https://techdocs.akamai.com/app-platform/docs/platform-teams) are isolated tenants on the platform to support Development/DevOps teams, projects, and methodologies, like [DTAP](https://en.wikipedia.org/wiki/Development,_testing,_acceptance_and_production). A Team gets access to the Console, which provides access to self-service features and the shared apps available on the platform.
60
61
61
62
When working in the context of an admin-level Team, users can create and access resources in any namespace. When working in the context of a non-admin Team, users can only create and access resources used in that Team’s namespace.
62
63
@@ -116,7 +117,7 @@ Repeat the same steps for installing the MySQL service on your cluster.
116
117
117
118
Separate Workloads are created forMySQL and WordPressin order to deploy a persistent database and site, respectively. Both Workloads require passwords, so to prevent the passwords from being stored unencrypted, Sealed Secrets are created for each first.
118
119
119
-
[Sealed Secrets](https://apl-docs.net/docs/for-devs/console/secrets) are encrypted Kubernetes Secrets stored in the Values Git repository. When a Sealed Secret is created in the Console, the Kubernetes Secret will appear in the Team's namespace.
120
+
[Sealed Secrets](https://techdocs.akamai.com/app-platform/docs/team-secrets) are encrypted Kubernetes Secrets stored in the Values Git repository. When a Sealed Secret is created in the Console, the Kubernetes Secret will appear in the Team's namespace.
120
121
121
122
### Create a Sealed Secret to Store MySQL Passwords
122
123
@@ -184,7 +185,7 @@ Separate Workloads are created for MySQL and WordPress in order to deploy a pers
184
185
```
185
186
186
187
{{< note title="Managing Network Policies" >}}
187
-
The `networkPolicy` is disabled since all traffic is allowed by default. Rather than configuring `networkPolicy` values directly in the Workload config, this guide centrally manages all network policies using App Platform's [**Network Policies**](https://apl-docs.net/docs/for-ops/console/netpols) function.
188
+
The `networkPolicy` is disabled since all traffic is allowed by default. Rather than configuring `networkPolicy` values directly in the Workload config, this guide centrally manages all network policies using App Platform's [**Network Policies**](https://techdocs.akamai.com/app-platform/docs/team-network-policies) function.
188
189
{{< /note >}}
189
190
190
191
1. Click **Submit**. The Workload may take a few minutes to become ready.
@@ -275,7 +276,7 @@ Using the App Platform **Shell** feature, you can check to see if the WordPress
275
276
276
277
## Create a Service to Expose the WordPress Site
277
278
278
-
Creating a [Service](https://apl-docs.net/docs/for-devs/console/services) in App Platform configures NGINX’s Ingress Controller. This allows you to enable public access to services running internally on your cluster.
279
+
Creating a [Service](https://techdocs.akamai.com/app-platform/docs/team-services) in App Platform configures NGINX’s Ingress Controller. This allows you to enable public access to services running internally on your cluster.
279
280
280
281
1. Select **view**>**team** and **team**>**demo**in the top bar.
281
282
@@ -295,7 +296,7 @@ Creating a [Service](https://apl-docs.net/docs/for-devs/console/services) in App
295
296
296
297
### Setting Up DNS
297
298
298
-
When creating a Service, DNS foryour site can be configure using a CNAME rather than using an external IP address. To do this, configure a CNAME entry with your domain name provider, and follow the stepsin our [Using a CNAME](https://apl-docs.net/docs/for-devs/console/services#using-a-cname) App Platform documentation.
299
+
When creating a Service, DNS foryour site can be configure using a CNAME rather than using an external IP address. To do this, configure a CNAME entry with your domain name provider, and follow the stepsin our [Using a CNAME](https://techdocs.akamai.com/app-platform/docs/configure-cname) App Platform documentation.
299
300
300
301
See our guide on [CNAME records](https://techdocs.akamai.com/cloud-computing/docs/cname-records) for more information on how CNAME records work.
0 commit comments