Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Virtual service desired wight in negative number #3470

Closed
2 tasks
Eslam-mohammed-anwar opened this issue Mar 25, 2024 · 0 comments · Fixed by #3467
Closed
2 tasks

Virtual service desired wight in negative number #3470

Eslam-mohammed-anwar opened this issue Mar 25, 2024 · 0 comments · Fixed by #3467
Labels
bug Something isn't working

Comments

@Eslam-mohammed-anwar
Copy link

Virtual service desired wight in negative number

Screenshot 2024-03-25 at 4 01 31 PM

it caused number of pods to reach more than 1000 pods even HPA have a max pods = 40

Checklist:

  • I've included steps to reproduce the bug.
  • I've included the version of argo rollouts.

Describe the bug

To Reproduce

Expected behavior

Screenshots

Version

Logs

# Paste the logs from the rollout controller

# Logs for the entire controller:
kubectl logs -n argo-rollouts deployment/argo-rollouts

# Logs for a specific rollout:
kubectl logs -n argo-rollouts deployment/argo-rollouts | grep rollout=<ROLLOUTNAME

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
1 participant
@Eslam-mohammed-anwar