Skip to content
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.

Deploy in the default circle create new pods for all modules running #1517

Open
joaoinaciozup opened this issue Dec 20, 2021 · 0 comments · May be fixed by #1532
Open

Deploy in the default circle create new pods for all modules running #1517

joaoinaciozup opened this issue Dec 20, 2021 · 0 comments · May be fixed by #1532
Assignees
Labels
bug Something isn't working

Comments

@joaoinaciozup
Copy link

Describe the bug
When I create a new release in the default circle it rollout all the pods in the circle.

To Reproduce
Steps to reproduce the behavior:

  1. Install charles with helm
  2. Configure the workspace (gcr registry, helm repository in a specific branch)
  3. Configure two modules
  4. Deploy the first module in the default circle
  5. Override release and deploy the second module in the default circle

Expected behavior
I expected that only the second module was deployed and the first module had no changes, but it create a new deployment for all the modules in the circle, this behaviour happens even if I deploy a module with an image tag that is already running (Image for this scenario attached)

Screenshots
image

Your Environment

  • CharlesCD version used: Tested on 1.0.0 and 1.0.1
  • Description of environment where CharlesCD is running: GKE (1.20.12-gke.1500)
  • Browser Name and version (if applicable):

Additional context

I noticed that when I applly the deploy a new deploymentId is assigned for the deployments that are running.

@joaoinaciozup joaoinaciozup added the bug Something isn't working label Dec 20, 2021
@thallesfreitaszup thallesfreitaszup linked a pull request Jan 17, 2022 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants