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

Update default listener to tls and strimzi CRD version to v1beta2 #50

Merged
merged 1 commit into from
Jul 15, 2022
Merged

Update default listener to tls and strimzi CRD version to v1beta2 #50

merged 1 commit into from
Jul 15, 2022

Conversation

haoxins
Copy link
Contributor

@haoxins haoxins commented Jul 15, 2022

relates to #49

@jonathansick jonathansick changed the title fix the defaults Update default listener to internal and strimzi CRD version to v1beta2 Jul 15, 2022
@jonathansick jonathansick self-requested a review July 15, 2022 15:35
Copy link
Member

@jonathansick jonathansick left a comment

Choose a reason for hiding this comment

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

Right. This is consistent with our Helm chart, so our Kustomize deployment should work the same way too.

@jonathansick jonathansick merged commit 96dc1af into lsst-sqre:main Jul 15, 2022
@jonathansick
Copy link
Member

I'll put this out in a 0.5.0 release.

@haoxins haoxins deleted the more-feilds branch July 15, 2022 15:46
@jonathansick
Copy link
Member

Oh, sorry I read this backwards (needed coffee!). I got the direction of the change wrong. I think I'll need to revert the default listener this for consistency with our Helm chart and what Rubin considers to be an ideal default; but document better that this setting is needed for a tls-secured listener.

@jonathansick jonathansick changed the title Update default listener to internal and strimzi CRD version to v1beta2 Update default listener to tls and strimzi CRD version to v1beta2 Jul 15, 2022
@jonathansick
Copy link
Member

I think I've got my head around what's happening with listeners, written up in #51. I'll get this out in a beta and see if it works for everyone.

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.

None yet

2 participants