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

chore(scheduler): use instrumentation config instead of application #1602

Merged
merged 2 commits into from
Oct 20, 2024

Conversation

blumamir
Copy link
Collaborator

This PR moves the scheduler component to use instrumentationconfigs instead of instrumentedapplications. There is an effort to merge them any only use one CRD - the instrumentationconfigs.

The content of the object is not examined, it only checks if we have any instrumentationconfigs or not. Thus it should be safe.

return ctrl.Result{}, err
}
numberOfInstrumentedApps := len(instrumentedApps.Items)
numberOfInstrumentedApps := len(instrumentedConfigs.Items)
Copy link
Contributor

Choose a reason for hiding this comment

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

numberOfInstrumentedApps -> numberOfInstrumentationConfigs

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's intentional. Each instrumentation config object represents an app

@blumamir blumamir merged commit b976b0a into odigos-io:main Oct 20, 2024
26 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