diff --git a/.devcontainer/installMoreTools.sh b/.devcontainer/installMoreTools.sh index 036f2c53..cae2566d 100755 --- a/.devcontainer/installMoreTools.sh +++ b/.devcontainer/installMoreTools.sh @@ -3,6 +3,8 @@ mkdir install-more-tools cd install-more-tools +yarn add dprint + SCORE_COMPOSE_VERSION=$(curl -sL https://api.github.com/repos/score-spec/score-compose/releases/latest | jq -r .tag_name) wget https://github.com/score-spec/score-compose/releases/download/${SCORE_COMPOSE_VERSION}/score-compose_${SCORE_COMPOSE_VERSION}_linux_amd64.tar.gz tar -xvf score-compose_${SCORE_COMPOSE_VERSION}_linux_amd64.tar.gz diff --git a/content/en/docs/How to/github.md b/content/en/docs/How to/github.md index 6eba4cba..8c6f6c18 100644 --- a/content/en/docs/How to/github.md +++ b/content/en/docs/How to/github.md @@ -22,7 +22,7 @@ To use the Score GitHub Action, add the following step to your [workflow](https: ```yaml steps: - - uses: score-spec/setup-score@v2 + - uses: score-spec/setup-score@v3 with: file: version: '' @@ -54,14 +54,14 @@ jobs: runs-on: ubuntu-latest steps: - - uses: score-spec/setup-score@v2 + - uses: score-spec/setup-score@v3 with: file: score-compose - version: '0.13.0' + version: 'latest' token: ${{ secrets.GITHUB_TOKEN }} - run: score-compose --version ``` -This installs version `0.13.0` of `score-compose`, adds it to `$PATH`, and runs `score-compose --version` to verify it is set up correctly. +This installs the `latest` version of `score-compose`, adds it to `$PATH`, and runs `score-compose --version` to verify it is set up correctly. The action caches the Score binary, so it won't need to download it each run. diff --git a/content/en/docs/How to/score-cicd-pipelines.md b/content/en/docs/How to/score-cicd-pipelines.md index 5ddcec0d..900e143b 100644 --- a/content/en/docs/How to/score-cicd-pipelines.md +++ b/content/en/docs/How to/score-cicd-pipelines.md @@ -77,7 +77,7 @@ jobs: steps: - uses: actions/checkout@v4 - uses: docker/setup-buildx-action@v3 - - uses: paulhatch/semantic-version@v5.0.3 + - uses: paulhatch/semantic-version@v5 id: semver - uses: docker/build-push-action@v5 with: @@ -98,10 +98,10 @@ The next set of steps focuses on testing with `score-compose`. This provides val This helps to maximize the chance that the "release" step to production succeeds and results in a working application. ```yaml - - uses: score-spec/setup-score@v2 + - uses: score-spec/setup-score@v3 with: file: score-compose - version: 0.15.6 + version: latest token: ${{ secrets.GITHUB_TOKEN }} - run: score-compose init - run: score-compose generate score.yaml --image=${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}:${{ steps.semver.outputs.version }} @@ -147,10 +147,10 @@ jobs: And finally, the steps to convert to Kubernetes manifests and deploy them. Notice that the `generate` call is setting the image to the tag that was just uploaded in the previous steps. The `azure/` actions are maintained by Azure, but are not Azure-specific and can deploy to any generic Kubernetes cluster as needed. Notice that this requires a `KUBECONFIG` secret variable set in the Github Actions workflow to authenticate with the target cluster. ```yaml -- uses: score-spec/setup-score@v2 +- uses: score-spec/setup-score@v3 with: file: score-k8s - version: 0.1.5 + version: latest token: ${{ secrets.GITHUB_TOKEN }} - uses: azure/k8s-set-context@v2 with: diff --git a/content/en/docs/How to/score-k8s/kind-cluster.md b/content/en/docs/How to/score-k8s/kind-cluster.md index 044fb014..f6787456 100644 --- a/content/en/docs/How to/score-k8s/kind-cluster.md +++ b/content/en/docs/How to/score-k8s/kind-cluster.md @@ -72,7 +72,7 @@ EOF From here, by using the [default provisioners with `score-k8s init`](/docs/score-implementation/score-k8s/resources-provisioners/), you will be able to use this `Gateway` by using the `route` object which will generate an `HTTPRoute` link to this `Gateway`. -This default `HTTPRoute` is assuming that `Gateway` is in the same `Namespace`, but if you want to use the [cross-Namespace Gateway](https://gateway-api.sigs.k8s.io/guides/multiple-ns/) approach, you will need to use [this community provisioner](https://github.com/score-spec/community-provisioners/blob/main/route/score-k8s/10-shared-gateway-httproute.provisioners.yaml) instead: +This default `HTTPRoute` is assuming that `Gateway` is in the same `Namespace`, but if you want to use the [cross-Namespace Gateway](https://gateway-api.sigs.k8s.io/guides/multiple-ns/) approach, you will need to use [this community provisioner](https://docs.score.dev/examples/resource-provisioners/community/route/score-k8s/template/route-with-shared-gateway/) instead: ```bash score-k8s init \ @@ -87,7 +87,7 @@ Install the Nginx Ingress controller in the Kind cluster: kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml ``` -From here, you can now use [this community provisioner](https://github.com/score-spec/community-provisioners/blob/main/route/score-k8s/10-ingress-route.provisioners.yaml) to generate an `Ingress` for the `route` resource instead of the default `HTTPRoute`: +From here, you can now use [this community provisioner](https://docs.score.dev/examples/resource-provisioners/community/route/score-k8s/template/ingress-route/) to generate an `Ingress` for the `route` resource instead of the default `HTTPRoute`: ```bash score-k8s init \ diff --git a/content/en/docs/community/_index.md b/content/en/docs/community/_index.md index 7845257f..8ae9a19d 100644 --- a/content/en/docs/community/_index.md +++ b/content/en/docs/community/_index.md @@ -26,6 +26,8 @@ We host [regular community meetings](https://github.com/score-spec/spec?tab=read ## Watch talks about Score +- _(Coming) [KubeCon India 2026 - The Death of the YAML-Engineer: Engineering "Invisible" Platforms With Crossplane and Score](https://sched.co/2IW4r)_ +- _(Coming) [KubeCon Europe 2026 - Unifying Inner & Outer Loops To Bridge the Gaps Between Devs & Ops With Microcks + Score - Laurent Broudoux, Microcks & Mathieu Benoit, Docker](https://sched.co/2CVxb)_ - [Cloud Native Rejekts NA 2025 - Make your Developer's Pains go Away, with the Right Level of Abstraction for your Platform](https://youtu.be/CLCK2lBpWa8) - [LF Live Webinar: From CI to Kubernetes Catalog: A Practical Guide to vCluster and GitOps](https://youtu.be/U4AgmEo3oV8) - [KubeCon EU 2025 - Score Lightning Talk](https://sched.co/1tcwp) [[video](https://youtu.be/Nq_PgPKZHsc?list=PLj6h78yzYM2MP0QhYFK8HOb8UqgbIkLMc)] diff --git a/content/en/docs/examples/included/backstage-score-compose.md b/content/en/docs/examples/included/backstage-score-compose.md index 29f76567..4075ed11 100644 --- a/content/en/docs/examples/included/backstage-score-compose.md +++ b/content/en/docs/examples/included/backstage-score-compose.md @@ -16,7 +16,7 @@ score-compose init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-compose/10-dns-with-url.provisioners.yaml ``` -The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-compose/10-dns-with-url.provisioners.yaml). +The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-url/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/backstage-score-k8s.md b/content/en/docs/examples/included/backstage-score-k8s.md index d725a0c8..809a2476 100644 --- a/content/en/docs/examples/included/backstage-score-k8s.md +++ b/content/en/docs/examples/included/backstage-score-k8s.md @@ -16,7 +16,7 @@ score-k8s init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-k8s/10-dns-with-url.provisioners.yaml ``` -The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-k8s/10-dns-with-url.provisioners.yaml). +The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-k8s/template/dns-with-url/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/dapr-score-compose.md b/content/en/docs/examples/included/dapr-score-compose.md index e30a2a3d..c6ee8413 100644 --- a/content/en/docs/examples/included/dapr-score-compose.md +++ b/content/en/docs/examples/included/dapr-score-compose.md @@ -17,7 +17,7 @@ score-compose init --no-sample \ --patch-templates https://raw.githubusercontent.com/score-spec/community-patchers/refs/heads/main/score-compose/dapr.tpl ``` -The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to seamlessly generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dapr-state-store/score-compose/10-redis-dapr-state-store.provisioners.yaml). +The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to seamlessly generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dapr-state-store/score-compose/template/redis-dapr-state-store/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/dapr-score-k8s.md b/content/en/docs/examples/included/dapr-score-k8s.md index 8439dc5a..655b3b93 100644 --- a/content/en/docs/examples/included/dapr-score-k8s.md +++ b/content/en/docs/examples/included/dapr-score-k8s.md @@ -16,7 +16,7 @@ score-k8s init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dapr-state-store/score-k8s/10-redis-dapr-state-store.provisioners.yaml ``` -The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dapr-state-store/score-k8s/10-redis-dapr-state-store.provisioners.yaml). +The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to generate a Dapr StateStore `Component` pointing to a Redis database: [`dapr-state-store` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dapr-state-store/score-k8s/template/redis/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/frontend-and-backend-score-compose.md b/content/en/docs/examples/included/frontend-and-backend-score-compose.md index 23efb170..6ad07934 100644 --- a/content/en/docs/examples/included/frontend-and-backend-score-compose.md +++ b/content/en/docs/examples/included/frontend-and-backend-score-compose.md @@ -17,7 +17,7 @@ score-compose init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-compose/10-dns-with-url.provisioners.yaml ``` -The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-compose/10-dns-with-url.provisioners.yaml) and `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-compose/10-service.provisioners.yaml). +The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-route/) and `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-compose/template/static-service/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/frontend-and-backend-score-k8s.md b/content/en/docs/examples/included/frontend-and-backend-score-k8s.md index e1f1fe04..f2bb4928 100644 --- a/content/en/docs/examples/included/frontend-and-backend-score-k8s.md +++ b/content/en/docs/examples/included/frontend-and-backend-score-k8s.md @@ -17,7 +17,7 @@ score-k8s init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-k8s/10-dns-with-url.provisioners.yaml ``` -The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://github.com/score-spec/community-provisioners/blob/main/dns/score-k8s/10-dns-with-url.provisioners.yaml) and `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-k8s/10-service.provisioners.yaml). +The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing two external files to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-k8s/template/dns-with-url/) and `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-k8s/template/static-service/). You can see the resource provisioners available by running this command: diff --git a/content/en/docs/examples/included/microservices-score-compose.md b/content/en/docs/examples/included/microservices-score-compose.md index 88de3cc0..7fc33aaa 100644 --- a/content/en/docs/examples/included/microservices-score-compose.md +++ b/content/en/docs/examples/included/microservices-score-compose.md @@ -16,7 +16,7 @@ score-compose init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/service/score-compose/10-service.provisioners.yaml ``` -The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-compose/10-service.provisioners.yaml). +The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-compose/template/static-service/). You can see the resource provisioners available by running this command: @@ -52,27 +52,27 @@ Convert the `score-*.yaml` files into a deployable `compose.yaml`, run the follo ```bash score-compose generate score-cart.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.5 score-compose generate score-currency.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.5 score-compose generate score-payment.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.5 score-compose generate score-email.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.5 score-compose generate score-productcatalog.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.5 score-compose generate score-shipping.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.5 score-compose generate score-ad.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.5 score-compose generate score-recommendation.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.5 score-compose generate score-checkout.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.5 score-compose generate score-frontend.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.5 score-compose generate score-loadgenerator.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.5 ``` The `generate` commands will add the input `score-*.yaml` workloads with a particular container image to the `.score-compose/state.yaml` state file and generate the output `compose.yaml`. @@ -206,17 +206,17 @@ docker ps ```none CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -2420e4a5b044 us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.3 "/src/server" 9 minutes ago 9 minutes ago 8080/tcp ob-frontend-frontend-1 -0c8705f6571a us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.3 "/app/build/install/…" 9 minutes ago Up 9 minutes 9555/tcp ob-ad-ad-1 -0d72556cc169 us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.3 "/bin/sh -c 'locust …" 9 minutes ago Up 9 minutes ob-loadgenerator-loadgenerator-1 -8c72e85b4c66 us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.3 "/src/checkoutservice" 9 minutes ago Up 9 minutes 5050/tcp ob-checkout-checkout-1 -2dd9df6fa024 us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.3 "/src/server" 9 minutes ago Up 9 minutes 3550/tcp ob-productcatalog-productcatalog-1 -a6d0ebc3aab2 us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.3 "node index.js" 9 minutes ago Up 9 minutes 50051/tcp ob-payment-payment-1 -e2511187e454 us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.3 "python recommendati…" 9 minutes ago Up 9 minutes 8080/tcp ob-recommendation-recommendation-1 -a4156abacd40 us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.3 "/app/cartservice" 9 minutes ago Up 9 minutes 7070/tcp ob-cart-cart-1 -2379e57ac8ca us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.3 "node server.js" 9 minutes ago Up 9 minutes 7000/tcp ob-currency-currency-1 -81efe5bcde69 us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.3 "python email_server…" 9 minutes ago Up 9 minutes 8080/tcp ob-email-email-1 -d83a61963aa6 us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.3 "/src/shippingservice" 9 minutes ago Up 9 minutes 50051/tcp ob-shipping-shipping-1 +2420e4a5b044 us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.5 "/src/server" 9 minutes ago 9 minutes ago 8080/tcp ob-frontend-frontend-1 +0c8705f6571a us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.5 "/app/build/install/…" 9 minutes ago Up 9 minutes 9555/tcp ob-ad-ad-1 +0d72556cc169 us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.5 "/bin/sh -c 'locust …" 9 minutes ago Up 9 minutes ob-loadgenerator-loadgenerator-1 +8c72e85b4c66 us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.5 "/src/checkoutservice" 9 minutes ago Up 9 minutes 5050/tcp ob-checkout-checkout-1 +2dd9df6fa024 us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.5 "/src/server" 9 minutes ago Up 9 minutes 3550/tcp ob-productcatalog-productcatalog-1 +a6d0ebc3aab2 us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.5 "node index.js" 9 minutes ago Up 9 minutes 50051/tcp ob-payment-payment-1 +e2511187e454 us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.5 "python recommendati…" 9 minutes ago Up 9 minutes 8080/tcp ob-recommendation-recommendation-1 +a4156abacd40 us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.5 "/app/cartservice" 9 minutes ago Up 9 minutes 7070/tcp ob-cart-cart-1 +2379e57ac8ca us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.5 "node server.js" 9 minutes ago Up 9 minutes 7000/tcp ob-currency-currency-1 +81efe5bcde69 us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.5 "python email_server…" 9 minutes ago Up 9 minutes 8080/tcp ob-email-email-1 +d83a61963aa6 us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.5 "/src/shippingservice" 9 minutes ago Up 9 minutes 50051/tcp ob-shipping-shipping-1 ed5f79d80259 mirror.gcr.io/redis:7-alpine "redis-server /usr/l…" 9 minutes ago Up 9 minutes 6379/tcp ob-redis-NYOMHD-1 6ee7b587922f mirror.gcr.io/nginx:1-alpine "/docker-entrypoint.…" 9 minutes ago Up 9 minutes 0.0.0.0:8080->80/tcp, [::]:8080->80/tcp ob-routing-K7ZrCr-1 ``` diff --git a/content/en/docs/examples/included/microservices-score-k8s.md b/content/en/docs/examples/included/microservices-score-k8s.md index d416be7a..6c1c7ed4 100644 --- a/content/en/docs/examples/included/microservices-score-k8s.md +++ b/content/en/docs/examples/included/microservices-score-k8s.md @@ -16,7 +16,7 @@ score-k8s init --no-sample \ --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/service/score-compose/10-service.provisioners.yaml ``` -The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `service` dependencies: [`service` provisioner](https://github.com/score-spec/community-provisioners/blob/main/service/score-k8s/10-service.provisioners.yaml). +The `init` command will create the `.score-k8s` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-k8s/resources-provisioners/" >}}) available. We are also importing one external file to support the `service` dependencies: [`service` provisioner](https://docs.score.dev/examples/resource-provisioners/community/service/score-k8s/template/static-service/). You can see the resource provisioners available by running this command: @@ -52,27 +52,27 @@ Convert the `score-*.yaml` files into a deployable `manifests.yaml`, run the fol ```bash score-k8s generate score-cart.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/cartservice:v0.10.5 score-k8s generate score-currency.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/currencyservice:v0.10.5 score-k8s generate score-payment.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/paymentservice:v0.10.5 score-k8s generate score-email.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/emailservice:v0.10.5 score-k8s generate score-productcatalog.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/productcatalogservice:v0.10.5 score-k8s generate score-shipping.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/shippingservice:v0.10.5 score-k8s generate score-ad.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/adservice:v0.10.5 score-k8s generate score-recommendation.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/recommendationservice:v0.10.5 score-k8s generate score-checkout.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/checkoutservice:v0.10.5 score-k8s generate score-frontend.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/frontend:v0.10.5 score-k8s generate score-loadgenerator.yaml \ - --image us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.3 + --image us-central1-docker.pkg.dev/google-samples/microservices-demo/loadgenerator:v0.10.5 ``` The `generate` command will add the input `score-*.yaml` workloads with a particular container image to the `.score-k8s/state.yaml` state file and generate the output `manifests.yaml`. diff --git a/content/en/docs/examples/microservices.md b/content/en/docs/examples/microservices.md index f4a6d35c..8d37e88b 100644 --- a/content/en/docs/examples/microservices.md +++ b/content/en/docs/examples/microservices.md @@ -33,7 +33,7 @@ flowchart TD ## Score files -We will describe each containerized application with its own Score file for each. The demo code can be found [here](https://github.com/Humanitec-DemoOrg/onlineboutique-demo/tree/main). +We will describe each containerized application with its own Score file for each. The demo code can be found [here](https://github.com/score-spec/examples/tree/main/samples/onlineboutique). Open your IDE and paste in the following `score-frontend.yaml` file, which describes the `frontend` containerized application exposed via a DNS that queries different other applications on each request: @@ -140,7 +140,7 @@ resources: type: redis ``` -Just two Score files have been illustrated above, you can grab the other Score files from [this GitHub repository](https://github.com/Humanitec-DemoOrg/onlineboutique-demo/tree/main/apps). +Just two Score files have been illustrated above, you can grab the other Score files from [this GitHub repository](https://github.com/score-spec/examples/tree/main/samples/onlineboutique). ## Deployment with `score-compose` and `score-k8s` diff --git a/content/en/docs/score implementation/score-compose/resources-provisioners.md b/content/en/docs/score implementation/score-compose/resources-provisioners.md index 1146e529..c2232bc3 100644 --- a/content/en/docs/score implementation/score-compose/resources-provisioners.md +++ b/content/en/docs/score implementation/score-compose/resources-provisioners.md @@ -36,11 +36,11 @@ To list the provisioners available from the `.score-compose` directory, run the | `service-port` | (any) | `port`, `workload` | `hostname`, `port` | Outputs a hostname and port for connecting to another workload. | | `volume` | (any) | (none) | `source`, `type` | Creates a persistent volume that can be mounted on a workload. | -The source code of these provisioners implementations can be found in the [`score-compose`'s default provisioners file](https://github.com/score-spec/score-compose/blob/main/internal/command/default.provisioners.yaml). +The full list of these `score-compose` and their source code provisioners can be found [here](https://docs.score.dev/examples/resource-provisioners?source=default&implementation=score-compose). ## Community provisioners -A list of provisioners authored and shared by the community can also be found [here](https://github.com/score-spec/community-provisioners). Users are encouraged to use them and contribute to this growing list of community provisioners: +A list of provisioners for `score-compose` authored and shared by the community can also be found [here](https://docs.score.dev/examples/resource-provisioners?source=community&implementation=score-compose). Users are encouraged to use them and contribute to this growing list of community provisioners: | Type | Class | Params | Outputs | Description | | --------------------------- | ----- | ----------------- | --------------- | ----------------------------------------------------------------------------------------- | diff --git a/content/en/docs/score implementation/score-k8s/resources-provisioners.md b/content/en/docs/score implementation/score-k8s/resources-provisioners.md index ad91efff..e9cd6900 100644 --- a/content/en/docs/score implementation/score-k8s/resources-provisioners.md +++ b/content/en/docs/score implementation/score-k8s/resources-provisioners.md @@ -33,11 +33,11 @@ To list the provisioners available from the `.score-k8s` directory, run the `sco | `service-port` | (any) | `port`, `workload` | `hostname`, `port` | Outputs a hostname and port for connecting to another workload. | | `volume` | (any) | (none) | `source` | Creates a persistent volume that can be mounted on a workload. | -The source code of these provisioners implementations can be found in the [`score-k8s`'s default provisioners file](https://github.com/score-spec/score-k8s/blob/main/internal/provisioners/default/zz-default.provisioners.yaml). +The full list of these `score-compose` provisioners and their source code can be found [here](https://docs.score.dev/examples/resource-provisioners?source=default&implementation=score-k8s). ## Community provisioners -A list of provisioners authored and shared by the community can also be found [here](https://github.com/score-spec/community-provisioners). Users are encouraged to use them and contribute to this growing list of community provisioners: +A list of `score-k8s` provisioners authored and shared by the community can also be found [here](https://docs.score.dev/examples/resource-provisioners?source=community&implementation=score-k8s). Users are encouraged to use them and contribute to this growing list of community provisioners: | Type | Class | Params | Outputs | Description | | --------------------------- | ----- | --------------------------------------------------------------------- | -------------------------------------- | --------------------------------------------------------------------------------------- |