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] upgrading upstream helm chart #270

Merged
merged 1 commit into from
Aug 11, 2023

Conversation

nicolastakashi
Copy link
Contributor

Description

Upgrading the upstream chart to use the latest coralogix otel helm chart

How Has This Been Tested?

Checklist:

  • I have updated the relevant Helm chart(s) version(s)
  • I have updated the relevant component changelog(s)
  • This change does not affect any particular component (e.g. it's CI or docs change)

Copy link
Contributor

@matej-g matej-g left a comment

Choose a reason for hiding this comment

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

Looks good, would you mind also updating the otel-integration chart? 🙏 Or prefer to do it separately?

Actually scratch that, since we have now 0.70.0 I will need to bump it for another feature, so no need.

otel-agent/k8s-helm/CHANGELOG.md Outdated Show resolved Hide resolved
@nicolastakashi nicolastakashi force-pushed the chore/upgrading-upstreamchart-otel branch from 672e560 to 642d2e5 Compare August 11, 2023 13:12
@nicolastakashi nicolastakashi force-pushed the chore/upgrading-upstreamchart-otel branch from 642d2e5 to 2f71613 Compare August 11, 2023 13:12
@nicolastakashi nicolastakashi force-pushed the chore/upgrading-upstreamchart-otel branch from 2f71613 to d07664c Compare August 11, 2023 13:13
@nicolastakashi nicolastakashi merged commit d756b3f into master Aug 11, 2023
5 checks passed
@nicolastakashi nicolastakashi deleted the chore/upgrading-upstreamchart-otel branch August 11, 2023 13:57
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