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
@@ -86,17 +86,29 @@ Before you begin, do the following to set up your environment:
86
86
87
87
Setting the `REPLICATED_APP` environment variable allows you to interact with the application using the Replicated CLI without needing to use the `--app` flag with every command.
88
88
89
-
## Get the Chart Archive and Create a Release
89
+
###Get the Chart Archive and Create a Release
90
90
91
91
1. Run the following command to download the SlackerNews Helm chart archive to a new `tutorial-helm-install` directory:
[View a larger version of this image](/images/enterprise-portal-installation-guide.png)
183
+
[View a larger version of this image](/images/enterprise-portal-installation-guide.png)
172
184
173
185
1. For instance name, enter a nickname for the instance.
174
186
175
-
1. For **Kubernetes Distribution**, select the distribution of your cluster where you will install SlackerNews.
187
+
1. For **Kubernetes Distribution**, select the distribution of your cluster where you will install SlackerNews. (If you are going to use Compatibility Matrix to create the cluster, select **Vanilla Kubernetes**).
176
188
177
189
1. For **Cluster Network Availability**, select **Outbound requests allowed**.
178
190
179
191
1. For **Registry Access**, select **My workstation can access the internet, the registry AND the cluster**.
180
192
181
193
1. Click **Next**.
182
194
183
-
##Create the Values File
195
+
### Install
184
196
185
-
1.Create a Helm values file to pass to the chart during installation:
197
+
1.If you brouhgt your own cluster, set kubectl context to the cluster where you want to install. If you are using Compatibility Matrix, do the following:
186
198
187
-
```bash
188
-
touch my-values.yaml
189
-
```
190
-
1. In the `my-values.yaml` file, copy and paste the following YAML:
1. In the `slackernews.domain` field, enter a hostname.
280
-
281
-
This is a required value for the application. For the purpose of this tutorial, the value that you provide does not need to be a real hostname. You will use a port forward to access SlackerNews in a browser after installation.
282
-
283
-
```yaml
284
-
# my-values.yaml
285
-
slackernews:
286
-
domain: "somedomain"
287
-
```
199
+
1. Create a kind cluster with version 1.34.0 of Kubernetes:
1. After the cluster is running, use the kubectl command provided to set your kubectl context to the cluster.
209
+
1. Run the first command to log in to the Replicated registry.
300
210
301
-
1.In the Enterprise Portal, for **Helm Online Install**, select the release version that you promoted (`0.0.1`).
211
+
1.Run the commands to install the preflight plugin and then run preflight checks in the cluster.
302
212
303
-
1. Copy and run the first command to log in to the Replicated registry.
213
+
1. Copy the install command and make the following changes:
214
+
* Remove the `--values my-values.yaml` flag. This is not necessary for the purpose of this tutorial because you do not need to pass a local values file to the chart.
215
+
* Add `--namespace slackernews --create-namespace` to install the application to the slackernews namespace on the cluster
304
216
305
-
1.Copy and run the commands to install and run preflight checks in the cluster.
217
+
1.Watch the application resources become available:
306
218
307
-
1. Run the install command to install SlackerNews in your cluster using the Helm CLI. Ensure that the path provided with the `--values` flag points to the `my-values.yaml` file that you created.
219
+
```bash
220
+
kubectl get all --namespace slackernews --watch
221
+
```
308
222
309
-
1. Run `kubectl get all -n slackernews` to see when services are running
223
+
1. Run the following command to port forward the slackernews NGINX service to local port 8080:
310
224
311
-
1. Run `kubectl port-forward --namespace slackernews svc/slackernews-nginx 8080:80` to port forward
0 commit comments