-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Labels
CIRelated to testingRelated to testingK8s/ToolsRelated to container/cloud native tools, orchestratorsRelated to container/cloud native tools, orchestratorsdevInvolves developmentInvolves developmentfeatureIssues created from the urunc teamIssues created from the urunc teamgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Milestone
Description
At the moment, we use latest as the tag for the urunc-deploy container image (image: ghcr.io/urunc-dev/urunc/urunc-deploy:latest) in urunc-deploy.yaml. This is not entirely correct.
We should use the tag that corresponds to the specific branch. For instance:
- When we push a new commit to main, we should be able to calculate the commit hash of the current tip of main, and use this as the tag to the container image built and pushed using the automated action. This is probably already implemented in: (kind of).
urunc/.github/workflows/build-latest.yml
Line 172 in 70411d2
# Determine the manifests' TAG - When we use urunc-deploy (
kubectl apply), we should be able to determine which tag to use. Maybe using kustomize, or some other trick/script to make sure that the tag corresponds to this specific version of the code. The same stands for feature/code altering branches that we would like to test.
Metadata
Metadata
Assignees
Labels
CIRelated to testingRelated to testingK8s/ToolsRelated to container/cloud native tools, orchestratorsRelated to container/cloud native tools, orchestratorsdevInvolves developmentInvolves developmentfeatureIssues created from the urunc teamIssues created from the urunc teamgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code