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

[receiver/k8scluster] e2e test #18394

Closed
Tracked by #15651
dmitryax opened this issue Feb 6, 2023 · 1 comment · Fixed by #23386
Closed
Tracked by #15651

[receiver/k8scluster] e2e test #18394

dmitryax opened this issue Feb 6, 2023 · 1 comment · Fixed by #23386

Comments

@dmitryax
Copy link
Member

dmitryax commented Feb 6, 2023

There is an e2e test for k8s attributes processor. We need to introduce similar tests for k8s cluster receiver and add it to the workflow. The common k8s utilities from the existing e2e test can be moved to a dedicated module in the contrib so it can be reused by the k8s cluster receiver as well.

@dmitryax dmitryax self-assigned this Feb 6, 2023
@fatsheep9146 fatsheep9146 changed the title [processor/k8scluster] e2e test [receiver/k8scluster] e2e test Feb 7, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants