TAP OSS Stack

Overview

This repo contains the source configuration built for a TAP OSS stack installation.
This Package repository has been tested on TCE 0.10.0 and TKGm 1.4 and works with the installed versions of Kapp Controller and doesnt require upgrading of Kapp Controller nor does it require secretgen inorder to work.

Why

Tanzu Application Platform is an amazing platform and is vastly built on open source projects. This repo brings together the Open source tools that are part of TAP into an easy installation method similar to TAP for the OSS community.
As not everyone has licensing for the TAP, this is meant as a way to play with the underlying technologies and understand at least in part what TAP "feels like".

Whats included:

This package repository includes the following packages:

1. tap-install.tap.oss - A single package that can install all other packages to allow for a simple installation like found in TAP
2. cartographer.tap.oss - A package based on the official package from the cartographer repo
3. dev-ns-preperation.tap.oss - A package for creating all the needed objects in a namespace (including the namespace itself if wanted) to run TAP OSS workloads
4. flux-source-controller.tap.oss - A package for installing Flux Source Controller
5. kpack-config.tap.oss - A package with configuration to setup kpack with Paketo buildpacks
6. ootb-supply-chains.tap.oss - A package that includes Supply chains for use in the cluster
7. tekton.tap.oss - A package to install Tekton to run pipelines within our supply chains
8. service-bindings.tap.oss - This is a package that allows simple binding of workloads to backend service using the service bindings project
9. cert-injection-webhook.tap.oss - This is a package that allows injection via webhook of CA certs into pods (used primarily for Kpack) to suppot registries and source control systems with self signed certs
10. kpack.tap.oss - This is the TCE Kpack package simply in the same repo to not have a requirement to install the TCE repo as well
11. knative-serving.tap.oss - This is the TCE Knative Serving package simply in the same repo to not have a requirement to install the TCE repo as well
12. cert-manager.tap.oss - This is the TCE Cert Manager package simply in the same repo to not have a requirement to install the TCE repo as well
13. contour.tap.oss - This is the TCE Contour package simply in the same repo to not have a requirement to install the TCE repo as well
14. rabbitmq-cluster-operator.tap.oss - [Seperate Installation] Deploys the RabbitMQ Cluster Operator and the Topology Operator. can be useful for the Service Bindings Supply Chain.
15. argo-cd.tap.oss - [Seperate Installation] Deploys ArgoCD. Can be useful when using GitOps Supply Chains for delivery in different clusters.
16. argo-workflows.tap.oss - [Seperate Installation] Deploys Argo Workflows. Can be used as an alternative to Tekton for steps in a supply chain.
17. jenkins.tap.oss - [Seperate Installation] Deploys Jenkins server. can be useful in custom supply chains in brownfield environments where jenkins would be used for testing / CI tasks

Installation instructions

TCE and TKGm 1.4+ users can skip to step 3 right away

If you are not running on a TKGm 1.4+ or TCE 0.9.1+ cluster, you must install the Tanzu CLI on your machine and install Kapp Controller in your cluster.

1. Install Tanzu CLI - Full instructions on TCE website

• Linux

curl -H "Accept: application/vnd.github.v3.raw" \
    -L https://api.github.com/repos/vmware-tanzu/community-edition/contents/hack/get-tce-release.sh | \
    bash -s v0.10.0 linux

• Mac

brew install vmware-tanzu/tanzu/tanzu-community-edition

• Windows

choco install tanzu-community-edition

2. Install Kapp Controller

kubectl apply -f https://github.com/vmware-tanzu/carvel-kapp-controller/releases/latest/download/release.yml

NOTE: Should work on any Kubernetes platform but has not been tested on all major platforms yet. if you have any issue with use on different platforms please open an issue

1. Create the TAP OSS namespace

kubectl create namespace tap-oss

2. Install the Package repository

tanzu package repository add tap-oss -n tap-oss --url ghcr.io/vrabbi/tap-oss-repo:0.2.4

3. Create a values file for installing the platform

cat <<EOF > tap-oss-values.yaml
contour:
  envoy:
    service:
      type: <FILL ME IN>
kpack:
  kp_default_repository: <FILL ME IN>
  kp_default_repository_password: <FILL ME IN>
  kp_default_repository_username: <FILL ME IN>
kpack_config:
  builder:
    tag: <FILL ME IN>
cert_injection_webhook:
  ca_cert_data: <FILL ME IN>
  http_proxy: <FILL ME IN>
  https_proxy: <FILL ME IN>
  no_proxy: <FILL ME IN>
knative:
  domain:
    name: <FILL ME IN>
    type: real
dev_ns_preperation:
  registry:
    username: <FILL ME IN>
    password: <FILL ME IN>
    server: <FILL ME IN>
  namespaces:
  - name: "default"
    exists: true
    createPipeline: true
    language: go
    gitops:
      enabled: true
      base64_encoded_ssh_key: <FILL ME IN>
      base64_encoded_known_hosts: ""
  - name: "example-ns-01"
    exists: false
    createPipeline: true
    language: go
    gitops:
      enabled: true
      base64_encoded_ssh_key: <FILL ME IN>
      base64_encoded_known_hosts: ""
ootb_supply_chains:
  image_prefix: <FILL ME IN>
  gitops:
    configure: true
    git_writer:
      message: "TAP OSS Based Update of app configuration"
      ssh_user: "git"
      server: "github.com"
      repository: <FILL ME IN>
      base64_encoded_ssh_key: <FILL ME IN>
      base64_encoded_known_hosts: ""
      branch: <FILL ME IN>
      username: <FILL ME IN>
      user_email: <FILL ME IN>
      port: ""
  testing:
    configure: true
disabled_packages:
  - ""
EOF

4. Update values file with your configuration values
       Check out the INSTALL_VALUES_EXPLANATION.md file for more info on the configuration parameters
5. Install the Platform

tanzu package install tap -n tap-oss -p tap-install.tap.oss -v 0.2.4 -f tap-oss-values.yaml

5. Wait for all package installs to reconcile

kubectl get pkgi -n tap-oss

6. Enjoy!
7. To see the status of the Platform you can use the script in the root of this repo "check-tap-oss-status.sh"

chmod +x check-tap-oss-status.sh
./check-tap-oss-status.sh

This will return output similar to:

Package Repository Status: Reconcile succeeded
Package Install Statuses:
  * TAP Installation Package: Reconcile succeeded
  * Cert Manager: Reconcile succeeded
  * Contour: Reconcile succeeded
  * Knative Serving: Reconcile succeeded
  * Flux Source Controller: Reconcile succeeded
  * Developer Namespace Preperation: Reconcile succeeded
  * Kpack: Reconcile succeeded
  * Kpack Configuration: Reconcile succeeded
  * OOTB Supply Chains: Reconcile succeeded
  * Service Bindings: Reconcile succeeded
  * Tekton: Reconcile succeeded
Custom Resource Statuses:
  * Kpack:
    * Cluster Stack: Ready = True
    * Cluster Store: Ready = True
    * Cluster Builder: Ready = True - (harbor.vrabbi.cloud/tap-oss/builder@sha256:5211a8a2324a1aeadb4ba6a00e10cc06d607a89c131d2c21f60ec4a2d1e1748b)
Configured Supply Chains:
  ootb-basic-supply-chain Selectors:
    apps.tanzu.vmware.com/workload-type: "web"

  ootb-basic-supply-chain-with-kaniko Selectors:
    apps.tanzu.vmware.com/image-builder: "kaniko"
    apps.tanzu.vmware.com/workload-type: "web"

  ootb-gitops-supply-chain Selectors:
    apps.tanzu.vmware.com/gitops: "true"
    apps.tanzu.vmware.com/workload-type: "web"

  ootb-svc-binding-native-k8s-deployment Selectors:
    apps.tanzu.vmware.com/has-db-binding: "true"
    apps.tanzu.vmware.com/native-k8s-deployment: "true"
    apps.tanzu.vmware.com/workload-type: "web"

  ootb-testing-supply-chain Selectors:
    apps.tanzu.vmware.com/has-tests: "true"
    apps.tanzu.vmware.com/workload-type: "web"

Deployed Workloads:
  petclinic-demo-app [default] Status:
    Ready = False
    Applied Supply Chain: ootb-svc-binding-native-k8s-deployment