Decouple release manifests + standardize release script #549
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #375 + is the first step towards kustomize support: #536
Change summary:
release/kubernetes-manifests.yaml
into separate files per service. This will support kustomize use cases (patches on individual services) including one I'm about to contribute for non gcp environments (fixing RecommendationService crashes under load-testing - "Request had insufficient authentication scopes." #359)dev-kubernetes-manifests/
and write tokubernetes-manifests/
.release/
so as to not break existing tutorials. The release pipeline generates both kubernetes manifests (separate files) and release/kubernetes-manifests (1 compiled file)push-and-deploy-latest
GH Actions workflow to push thelatest
images to thegoogle-samples
project, notonlineboutique-ci
. this way the release and latest images live in the same GCR repoTODO
release-tag
)