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

[CN-1372]: add note to TLS document about how to update TLS #251

Merged
merged 2 commits into from
Oct 17, 2024

Conversation

kutluhanmetin
Copy link
Contributor

No description provided.

Copy link

netlify bot commented Oct 15, 2024

Deploy Preview for pedantic-goldberg-f76ec1 ready!

Name Link
🔨 Latest commit c6c03eb
🔍 Latest deploy log https://app.netlify.com/sites/pedantic-goldberg-f76ec1/deploys/6710fd3136030b000832b658
😎 Deploy Preview https://deploy-preview-251--pedantic-goldberg-f76ec1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -74,3 +74,5 @@ include::ROOT:example$/hazelcast-tls.yaml[]
----
include::ROOT:example$/management-center-tls.yaml[]
----

NOTE: To update TLS certificates, it is required to delete and recreate the Hazelcast/Management Center custom resource.
Copy link
Contributor

@oliverhowell oliverhowell Oct 16, 2024

Choose a reason for hiding this comment

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

Suggested change
NOTE: To update TLS certificates, it is required to delete and recreate the Hazelcast/Management Center custom resource.
NOTE: To update TLS certificates, you need to delete and recreate the appropriate custom resource in Hazelcast Platform or Management Center.

Is it either the Hazelcast or MC resource you need to delete or both? The / is ambiguous here...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

TLS certificates are applicable for both CRs. So whichever you created you should delete it and recreate.

Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think of update suggestion then?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this should be enough: NOTE: To update TLS certificates, you need to delete and recreate the appropriate custom resource, WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yep, ship it!

Copy link
Contributor

@oliverhowell oliverhowell left a comment

Choose a reason for hiding this comment

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

Approving in advance

@kutluhanmetin kutluhanmetin merged commit c6f2d7c into main Oct 17, 2024
4 of 6 checks passed
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.

3 participants