Merge pull request #2521 from Guaris/rc-v.0.14

[Release Candidate] v0.14
linode · Jun 5, 2019 · 3184a84 · 3184a84
2 parents b9dc0b7 + 4fe6950
commit 3184a84
Show file tree

Hide file tree

Showing 45 changed files with 1,636 additions and 132 deletions.
diff --git a/docs/applications/containers/beginners-guide-to-LXD/apache-lxd-banner-image.jpg b/docs/applications/containers/beginners-guide-to-LXD/apache-lxd-banner-image.jpg
diff --git a/...ns/containers/beginners-guide-to-LXD/apache-server-running-in-lxd-container.png b/...ns/containers/beginners-guide-to-LXD/apache-server-running-in-lxd-container.png
diff --git a/docs/applications/containers/beginners-guide-to-LXD/index.md b/docs/applications/containers/beginners-guide-to-LXD/index.md
diff --git a/...cations/containers/how-to-deploy-kubernetes-on-linode-with-rancher-2-2/index.md b/...cations/containers/how-to-deploy-kubernetes-on-linode-with-rancher-2-2/index.md
@@ -410,7 +410,7 @@ To test out deploying an app on your new cluster, launch the WordPress app from
 Avoid using symbols in the password you enter, as some symbols can cause syntax errors for this Rancher chart.
 {{< /note >}}
 
-1.  In the **Database Settings** section, enter a password for WordPress' database user. Then set **MariaDB Persistent Volume Enabled** to **True** and select the **linode-block-storage** option from the **Default StorageClass for MariaDB** dropdown menu:
+1.  In the **Database Settings** section, enter a password for WordPress' database user. Then set **MariaDB Persistent Volume Enabled** to **True**, and select the **Use the default class** option from the **Default StorageClass for MariaDB** dropdown menu:
 
     ![Rancher WordPress setup form - Database Settings](wordpress-app-form-database-settings.png "Rancher WordPress setup form - Database Settings")
 
@@ -446,6 +446,13 @@ The default value for the **MariaDB Volume Size** field is 8GiB, but the minimum
 
     Your WordPress site should open in a new browser tab.
 
+    {{< note >}}
+If using the Toronto data center, you will need to manually update the HTTP NodeBalancer's endpoint URL to use the data center's short form name. Replace the `toronto1` portion of the URL with `tor1`. An updated example URL will appear as follows:
+
+`http://nb-192-0-2-0.tor1.nodebalancer.linode.com`
+    {{< /note >}}
+
+
 1.  Visit the wp-login.php page on your site (e.g. at `http://your-nodebalancer-name.newark.nodebalancer.linode.com/wp-login.php`). You should be able to login with the WordPress admin username and password you specified earlier in the app's form.
 
     {{< note >}}
@@ -526,6 +533,7 @@ Rancher also provides an easy way to scale your app's deployments:
 
     ![Rancher deployed apps list - WordPress app completed provisioning](default-project-app-view-wordpress-provisioned-link-highlighted.png "Rancher deployed apps list - WordPress app completed provisioning")
 
+
 1.  In the **Workloads** section, click on the **wordpress-wordpress** link in the **Name** column for that deployment:
 
     ![Rancher WordPress workloads - deployment name highlighted](wordpress-app-wordpress-workload-link-highlighted.png "Rancher WordPress workloads - deployment name highlighted")
@@ -536,6 +544,11 @@ Rancher also provides an easy way to scale your app's deployments:
 
 1.  A second pod will appear in the **Pods** section on this page, and there will be an **Updating** label at the top of the page. You may see a series of warning messages about the new pod not being available. Eventually, the new pod will be labelled as **Running**.
 
+
+{{< note >}}
+Rancher does not currently support interacting directly with Linode Volumes via its user interface. However, the scaling method described in this section of the guide will apply complete replication to your application and volumes.
+{{< /note >}}
+
 ## Set Up GitHub Authentication
 
 In addition to manually creating users that can access your Rancher application, you can also enable GitHub authentication and then invite GitHub users:

diff --git a/...-kubernetes-on-linode-with-rancher-2-2/wordpress-app-form-database-settings.png b/...-kubernetes-on-linode-with-rancher-2-2/wordpress-app-form-database-settings.png
diff --git a/...plications/containers/how-to-monitor-containers-with-the-elastic-stack/index.md b/...plications/containers/how-to-monitor-containers-with-the-elastic-stack/index.md
diff --git a/...ow-to-monitor-containers-with-the-elastic-stack/kibana-container-dashboards.png b/...ow-to-monitor-containers-with-the-elastic-stack/kibana-container-dashboards.png
diff --git a/...ntainers/how-to-monitor-containers-with-the-elastic-stack/kibana-dashboards.png b/...ntainers/how-to-monitor-containers-with-the-elastic-stack/kibana-dashboards.png
diff --git a/...containers/how-to-monitor-containers-with-the-elastic-stack/kibana-discover.png b/...containers/how-to-monitor-containers-with-the-elastic-stack/kibana-discover.png
diff --git a/...ers/how-to-monitor-containers-with-the-elastic-stack/kibana-docker-overview.png b/...ers/how-to-monitor-containers-with-the-elastic-stack/kibana-docker-overview.png
diff --git a/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-docker-resources.png b/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-docker-resources.png
diff --git a/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-filebeat-default.png b/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-filebeat-default.png
diff --git a/...ners/how-to-monitor-containers-with-the-elastic-stack/kibana-filebeat-index.png b/...ners/how-to-monitor-containers-with-the-elastic-stack/kibana-filebeat-index.png
diff --git a/...ainers/how-to-monitor-containers-with-the-elastic-stack/kibana-initial-page.png b/...ainers/how-to-monitor-containers-with-the-elastic-stack/kibana-initial-page.png
diff --git a/...ainers/how-to-monitor-containers-with-the-elastic-stack/kibana-landing-page.png b/...ainers/how-to-monitor-containers-with-the-elastic-stack/kibana-landing-page.png
diff --git a/...ntainers/how-to-monitor-containers-with-the-elastic-stack/kibana-management.png b/...ntainers/how-to-monitor-containers-with-the-elastic-stack/kibana-management.png
diff --git a/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-nginx-dashboards.png b/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-nginx-dashboards.png
diff --git a/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-nginx-metricbeat.png b/...rs/how-to-monitor-containers-with-the-elastic-stack/kibana-nginx-metricbeat.png
diff --git a/docs/applications/containers/install-docker-ce/index.md b/docs/applications/containers/install-docker-ce/index.md
@@ -47,6 +47,12 @@ sub   4096R/F273FCD8 2017-02-22
 
         sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
 
+    {{< note >}}
+For Ubuntu 19.04 if you get an `E: Package 'docker-ce' has no installation candidate` error this is because the stable version of docker for is not yet available. Therefore, you will need to use the edge / test repository.
+{{< /note >}}
+
+        sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable edge test"
+
 6.  Update your package index and install Docker CE:
 
         sudo apt update