06/07/2021, 11:32 AM
Hi all, we are trying to use Pulumi Kubernetes Operator to enable commit SHA based deployments in our AKS clusters. It seems to work all fine when we do commit and trigger the deployments based on that on local environment. However, this doesn't work in CI/CD environments as we are committing the same environment repo with aggressive git PRs/CI builds and the same stack file is being updated with the next container image version which leads to conflict issues. Is there a way to get around this issue or get rid if this approach altogether? Is there a way to watch for published images in container registry and then trigger deployments/image version change as in other gitops tools like FluxCD, ArgoCD, etc? Any help would be much appreciated.