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

[v1.11] Explicitly disable CQL over TLS (that never worked but breaks backups) #1675

Closed
tnozicka opened this issue Jan 4, 2024 · 3 comments · Fixed by #1817
Closed

[v1.11] Explicitly disable CQL over TLS (that never worked but breaks backups) #1675

tnozicka opened this issue Jan 4, 2024 · 3 comments · Fixed by #1817
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@tnozicka
Copy link
Member

tnozicka commented Jan 4, 2024

backport #1674

@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jan 4, 2024
@tnozicka tnozicka added kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jan 4, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jan 4, 2024
@tnozicka tnozicka changed the title [v1.11] Explicitly disable CQL over TLS [v1.11] Explicitly disable CQL over TLS (that never worked but breaks backups) Jan 4, 2024
@tnozicka tnozicka added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 19, 2024
@rzetelskik
Copy link
Member

@tnozicka this would require #1801 to be backported to 1.11 as well. Are we good to backport it?

@tnozicka
Copy link
Member Author

deps bump is ok

@rzetelskik
Copy link
Member

#1817 merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
2 participants