Add Pipelines Example to resources

This will help make the bootstrap folder more of a one-stop-shop for additional documentation.

README.md

@@ -106,4 +106,5 @@ One other common pattern we anticipate is for separate suborganizations each sha
 There's a few common things you'll often need to solve when managing kubernetes.  We've collected a lot of tested setups that you can adapt into your own environments.  In particular, we've provided resources for setting up:
 
 * monitoring - full loki + prometheus agent setup and how to connect them both to your instance of the console
-* OPA policy management - example yaml setup for OPA Gatekeeper and various constraints to meet common important benchmarks. 
+* OPA policy management - example yaml setup for OPA Gatekeeper and various constraints to meet common important benchmarks.
+* pipelines - a full PR Automation pipeline setup inclusive of using global services as well that should help testdrive some of the more advanced change management capabilities of the platform.

resources/pipelines/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

resources/pipelines/Makefile

@@ -0,0 +1,9 @@
+setup-k3s: # sets up a k3s cluster
+	@read -p "cluster name: " name; \
+	k3d cluster create $$name --image docker.io/rancher/k3s:v1.26.11-k3s2; \
+	plural cd clusters bootstrap --name $$name
+
+login: # logs in w/ plural cli
+	@read -p "Console url: " url;
+	@read -p "Console access token: " token;
+	@plural cd login --url $$url --token $$token

resources/pipelines/README.md

@@ -0,0 +1,56 @@
+# Pipelines Demo
+
+This is a very trivial demo to show a simple helm chart pipeline, it has a few main components:
+
+* wrapper service that would point to the `/services` directory that will sync everything in
+* service under `/dev` with a service deployment CRD and global service CRD to set up a global service for your dev tier. Note the tags for the GlobalService CRD there.
+* service under `/prod` with a service deployment CRD and global service CRD to set up a global service for your prod tier.  Note the tags for the GlobalService CRD there.
+* service under `/pipeline` that configures the pipelines CRDs needed to automate promotion between them.
+
+The dev service sets up a deployment for all clusters in the dev tier of the fleet, any updates to that subfolder will propagate there.  Similarly for the prod service.  This is configured to be manually git-ops'ed, so you'll have to specify all changes in this repo.
+
+Note this uses a git-vendored helm chart to make things as flexible as possible.  This approach is perfectly compatible w/ sourcing charts from helm repositories defined as Flux `HelmRepository` crds as well, and our docs should show an example of that as well.
+
+## The Pipeline
+
+The pipeline is designed to be PR-driven to maintain GitOps purity.  This involves a Pipeline CRD defining the pipeline, where each stage points to a PRAutomation as its promotion criteria, and a PipelineContext.  To trigger the pipeline, you can simply modify `spec.context` w/in the PipelineContext, and once the CRD is synced, it'll start initiating the necessary PR's.
+
+## Setting It Up Yourself
+
+TLDR, fork or add this repo to your console and then create a service named `pipeline-demo` under the `infra` namespace in your management cluster, pointing to the `/services` subfolder.
+
+If you might need to be delicate about namespace creation, just grep for `namespace:` for all the namespaces used and create them manually.  You should also create the `gh-test` ScmConnection in your console manually, or rewire it to an existing one in the `pipeline/prautomation.yaml` file's `scmConnectionRef` field.
+
+`dev/podinfo.yaml` and `prod/podinfo.yaml` are currently wired to `k3s-test` by default.  Just switch that name to a cluster you already have, and potentially you might need to create the `Cluster` crds for them, eg:
+
+```yaml
+apiVersion: deployments.plural.sh/v1alpha1
+kind: Cluster
+metadata:
+  name: k3s-test
+  namespace: infra
+spec:
+  handle: k3s-test
+```
+
+We've already created those in `services/clusters.yaml` but you're free to rename or remove them.
+
+## Setting up a test fleet
+
+One easy way to test this out is to use a few local k3d clusters. k3d is a version of k3s meant to run entirely in docker, and is a bit more feature-rich than KIND.  The process to set it up is simple, you'll first want to install k3d here: https://k3d.io/v5.6.0/#releases, then we've added a small make file with targets to create a cluster and install an agent easily.  You'll first want to run:
+
+```sh
+make login
+```
+
+That will log in your Plural CLI to the console (go to `/profile/access-tokens` to create a token).  Then your can run:
+
+```sh
+make setup-k3s
+```
+
+To create a new named k3s cluster.  If for whatever reason you fail to install the agent properly, you can always redrive the installation with `plural cd clusters reinstall {cluster-name}`
+
+## Notifications Setup
+
+We also added a commented setup for notifications routing in `services/notifications.yaml`, it expects you to have already created a notification sink named `slack`, which can be done in the notifications tab of the console UI most easily.

resources/pipelines/dev/global.yaml

@@ -0,0 +1,11 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: GlobalService
+metadata:
+  name: pipeline-podinfo-dev
+  namespace: dev
+spec:
+  serviceRef:
+    name: podinfo
+    namespace: dev
+  tags:
+    tier: dev

resources/pipelines/dev/podinfo.yaml

@@ -0,0 +1,23 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: ServiceDeployment
+metadata:
+  name: podinfo
+  namespace: dev
+spec:
+  name: podinfo
+  namespace: podinfo
+  git:
+    folder: podinfo
+    ref: main
+  repositoryRef:
+    kind: GitRepository
+    name: demo
+    namespace: infra
+  helm:
+    values:
+      image:
+        tag: 6.5.3 # VERSION
+  clusterRef:
+    kind: Cluster
+    name: k3s-test # change this to the appropriate name for your main test cluster
+    namespace: infra

resources/pipelines/pipeline/context.yaml

@@ -0,0 +1,10 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: PipelineContext
+metadata:
+  name: podinfo-pipeline-context
+spec:
+  pipelineRef:
+    name: podinfo
+    namespace: podinfo-pipeline
+  context:
+    version: 6.5.3

resources/pipelines/pipeline/pipeline.yaml

@@ -0,0 +1,28 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: Pipeline
+metadata:
+  name: podinfo
+spec:
+  stages:
+    - name: dev
+      services:
+        - serviceRef:
+            name: podinfo
+            namespace: dev
+          criteria:
+            prAutomationRef:
+              name: podinfo-pipeline-automation
+    - name: prod
+      services:
+        - serviceRef:
+            name: podinfo
+            namespace: prod
+          criteria:
+            prAutomationRef:
+              name: podinfo-pipeline-automation
+  edges:
+    - from: dev
+      to: prod
+      gates:
+      - name: approval-gate
+        type: APPROVAL

resources/pipelines/pipeline/prautomation.yaml

@@ -0,0 +1,21 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: PrAutomation
+metadata:
+  name: podinfo-pipeline-automation
+spec:
+  name: podinfo-pipeline-automation
+  documentation: Updates the podinfo service to a specified helm version for any pipeline stage
+  updates:
+    regexReplacements:
+    - regex: "tag: (.*) # VERSION"
+      file: "{{ context.pipeline.stage.name }}/podinfo.yaml"
+      replacement: "tag: {{ context.version }} # VERSION"
+  scmConnectionRef:
+    name: gh-test # or whatever you might have named this
+  title: "Updating pod info prod helm version to {{ context.version }} (stage={{ context.pipeline.stage.name }})"
+  message: "Updating pod info prod helm version to {{ context.version }} (stage={{ context.pipeline.stage.name }})"
+  identifier: pluralsh/pipelines-demo
+  configuration:
+  - name: version
+    type: STRING
+    documentation: The helm chart version to use

resources/pipelines/pipeline/scmconnection.yaml

@@ -0,0 +1,7 @@
+apiVersion: deployments.plural.sh/v1alpha1
+kind: ScmConnection
+metadata:
+  name: gh-test
+spec:
+  name: gh-test
+  type: GITHUB