feat(alpha): create alpha warning & apply it to pages (spinnaker#569)

Author: lwander

_includes/alpha

@@ -0,0 +1,11 @@
+<blockquote class="warning">
+  <p>
+    The contents of this page refer to alpha features in Spinnaker
+    {{ include.version }}.
+  </p>
+  <p>
+    This means we are working on their stability and usability, as well as
+    possibly adding or changing features. Expect rough edges, and file <a
+    href="https://github.com/spinnaker/spinnaker/issues">issues</a> as needed.
+  </p>
+</blockquote>

guides/tutorials/codelabs/kubernetes-v2-source-to-prod/index.md

@@ -5,9 +5,9 @@ sidebar:
   nav: guides
 ---
 
-{% include toc %}
+{% include alpha version="1.6" %}
 
-> __☞ Note__: This codelab requires Spinnaker 1.6 or later.
+{% include toc %}
 
 In this codelab you will configure:
 

guides/user/kubernetes-v2/deploy-manifest/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: guides
 ---
 
+{% include alpha version="1.6" %}
+
 {% include toc %}
 
 This guide is meant to show you the very basics of how to deploy a Kubernetes

guides/user/triggers/gcs/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: guides
 ---
 
+{% include alpha version="1.6" %}
+
 {% include toc %}
 
 This guide explains how to configure Spinnaker to trigger pipelines based on

reference/artifacts/in-kubernetes-v2/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: reference
 ---
 
+{% include alpha version="1.6" %}
+
 {% include toc %}
 
 Artifacts play an important role in the Kubernetes Provider V2. Everything from

reference/artifacts/in-pipelines/index.md

@@ -5,14 +5,16 @@ sidebar:
   nav: reference
 ---
 
-{% include toc %}
+{% include alpha version="1.6" %}
 
 {% include
    warning 
    content="Much of the behavior described here depends on looking up execution
    history in Redis. Deleting recent executions from Redis can cause
    unexpected behavior."
- %}
+%}
+
+{% include toc %}
 
 Now that you have an idea of [what an artifact is](/reference/artifacts/) in Spinnaker, you need to
 understand how it's used within pipelines. An artifact arrives in a pipeline execution either from an external trigger (for example, a Docker image pushed to registry) or by getting fetched by a stage. That artifact is then consumed by downstream stages based on pre-defined behavior.

reference/artifacts/types/overview/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: reference
 ---
 
+{% include alpha version="1.6" %}
+
 While an artifact can reference any remote, deployable resource, we have
 first-class support for in the form of:
 

reference/providers/kubernetes-v2/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: reference
 ---
 
+{% include alpha version="1.6" %}
+
 {% include toc %}
 
 This article describes how the Kubernetes provider v2 works, and how it differs

setup/install/providers/kubernetes-v2/index.md

@@ -5,6 +5,8 @@ sidebar:
   nav: setup
 ---
 
+{% include alpha version="1.6" %}
+
 {% include toc %}
 
 The Spinnaker Kubernetes V2 provider fully supports manifest-based deployments.