From bdd1046cc920f8ec9fd1ca491fbc6dcd1928a2de Mon Sep 17 00:00:00 2001 From: Ben Meier Date: Fri, 21 Jun 2024 08:59:21 +0100 Subject: [PATCH] chore: added managed score note --- content/en/docs/How to/score-cicd-pipelines.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/en/docs/How to/score-cicd-pipelines.md b/content/en/docs/How to/score-cicd-pipelines.md index b6d1b2b..5ddcec0 100644 --- a/content/en/docs/How to/score-cicd-pipelines.md +++ b/content/en/docs/How to/score-cicd-pipelines.md @@ -164,6 +164,12 @@ And finally, the steps to convert to Kubernetes manifests and deploy them. Notic manifests: ./manifests ``` +With the Score file in this example, the generated `manifests.yaml` file contains: + +- `apps/v1/Deployment` - the app itself +- `v1/Service` - the internal service +- `gateway.networking.k8s.io/v1/HTTPRoute` - the HTTP route from the ingress DNS name to the service + This workflow can now test, push, and deploy a Score application. However, there is a problem that remains: the `.score-k8s/state.yaml` file. ### Maintaining `score-k8s` state @@ -190,3 +196,9 @@ jobs: concurrency: group: ${{ github.workflow }}-${{ github.ref }} ``` + +### Moving to a managed Score implementation + +Managing the local `state.yaml` file is a risk. It may cause issues when concurrent deployments occur or if a workflow fails unexpectedly. Managed Score implementations and services are responsible for storing and converting any related resource state on behalf of the deployment and ensuring it is correctly shared between deployments. + +When using one of these managed services, the Github Actions workflow can be modified to replace the `score-k8s` and `kubectl` invocations.