cluster-template-test's Introduction

cluster-repo-template

A template repository for a civic cloud cluster

After cloning this template

Customize email in 2 places in cert-manager.issuers.yaml
Customize hostname in 2 places in grafana/release-values.yaml
Add a secret named BOT_GITHUB_TOKEN containing a GitHub token that can write to the repository (this is needed for a workflow to be triggered by another workflow)
1. Create or reuse GitHub bot user with write access to the cluster repository
2. Grant the GitHub bot user the write access to the cluster repository, and ensure that its invitation is accepted
3. Create a Personal Access Token under the GitHub bot user with the repo and workflow scopes using a classic token with no expiration
4. Save the generated Personal Access Token to a secret called BOT_GITHUB_TOKEN under the cluster repository
Add a secret named KUBECONFIG_BASE64 containing connection and authentication details for writing manifests to your Kubernetes cluster
1. Follow IaaS provider's instructions for setting up your local kubectl client to administer the provisioned Kubernetes cluster
2. Manually apply github-actions.serviceaccount.yaml using your local kubectl client to initialize the service account that GitHub Actions will use to handle deployments going forward:
```
kubectl apply -f ./github-actions.serviceaccount.yaml
```
3. Install the view-serviceaccount-kubeconfig plugin for kubectl to simplify generating a KUBECONFIG for a service account:
```
 kubectl krew install view-serviceaccount-kubeconfig
```
4. Create a token and generate a base64-encoded KUBECONFIG file from it:
```
kubectl --namespace kube-system create token github-actions \
    | kubectl view-serviceaccount-kubeconfig \
    | base64
```
5. Save the generated base64-encoded string to a secret called KUBECONFIG_BASE64 under the cluster repository

Recommend Projects