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.

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

Use GOMAXPROCS in gateway based on limits.cpu #1989

Merged
merged 5 commits into from
Dec 15, 2024

Conversation

RonFed
Copy link
Collaborator

@RonFed RonFed commented Dec 15, 2024

Comment on lines 106 to 109
- name: Odigos pipeline ready
try:
- assert:
file: ../../common/assert/pipeline-ready.yaml
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This guaranteed that we do not progress until the pipeline is ready.
Wonder if removing the assert can cause issues

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this step back, but only to make sure all the pods are ready, not asserting all the pods spec.
The full pipeline ready assert will be after the upgrade as before

tests/common/assert/pipeline-ready.yaml Show resolved Hide resolved
@blumamir blumamir merged commit b9b8b70 into odigos-io:main Dec 15, 2024
30 of 31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants