-
Notifications
You must be signed in to change notification settings - Fork 463
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
Ensuring the collector behavior remains consistent when mTLS feature gate is enabled but TA is not deployed #3496
base: main
Are you sure you want to change the base?
Conversation
Some test failures, but i think this is a fine fix for now. |
Pretty sure the CI test failure has nothing to do with the code changes. |
It looks like the only unit tests failing are ones related to the mTLS feature, so that would be quite the coincidence. |
Sorry, my bad. |
@ItielOlenick could you add a changelog entry? I wouldn't mind seeing a simple e2e test with the flag enabled but |
You got it. |
@swiatekm anything missing? |
You said you'd add an e2e test, but I don't see it in this PR. |
Sorry, i misread that for tests in general. |
Can you rebase your changes on main? Github doesn't show this in the diff, but your branch has changelog fragments from before the most recent release. |
…en-TA-is-not-deployed-and-mTLS-feature-gate-is-enabled
Done |
The changelog issue is fixed in #3595, so you won't need to delete the entry file after that's merged. |
Description:
Ensuring the collector behavior remains consistent when mTLS feature gate is enabled but TA is not deployed
Link to tracking Issue(s):
operator.targetallocator.mtls
results in non-existent certificate mounts for non-Prometheus collectors #3456Testing:
Local
Documentation:
No documentation changes needed