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

Backport of Fix consul-telemetry-collector deployments to non-default namespaces into release/1.1.x #3266

Closed
wants to merge 3 commits into from

Conversation

jjti
Copy link
Contributor

@jjti jjti commented Nov 27, 2023

This is a manually created backport for #3215

The auto-gen one failed: #3246

In a previous PR to consul-k8s the cloud observability tests were changed, but that wasn't backported. Because this backport includes acceptance test changes.. I'm also backporting those changes: #2946

@jjti jjti marked this pull request as ready for review November 27, 2023 19:16
@jjti jjti enabled auto-merge (squash) November 27, 2023 19:16
@jjti jjti changed the title Fix consul-telemetry-collector deployments to non-default namespaces … Backport of Fix consul-telemetry-collector deployments to non-default namespaces into release/1.1.x Nov 27, 2023
@jjti jjti added the pr/no-changelog PR does not need a corresponding .changelog entry label Nov 27, 2023
@jjti jjti marked this pull request as draft November 27, 2023 19:31
auto-merge was automatically disabled November 27, 2023 19:31

Pull request was converted to draft

@jjti jjti added the pr/no-backport signals that a PR will not contain a backport label label Nov 27, 2023
@jjti
Copy link
Contributor Author

jjti commented Nov 27, 2023

closing because GH is having an issue and it's faster to just make a new pr

@jjti jjti closed this Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant