DOC-425 - Review and update Operator docs #344
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for pedantic-goldberg-f76ec1 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Rob-Hazelcast
commented
Nov 26, 2025
| You can configure Member and Client Protocol interfaces as well as WAN Protocol socket ports using Operator. | ||
|
|
||
| == Configuring Member and Client Protocol Interfaces | ||
| // RJS: So you can't configure REST or Memcache with Operator? Should be more explicit than just leaving them out. |
| To access the Management Center dashboard, open the browser at address `http://$MANCENTER_IP:8080`. | ||
| . To access the Management Center dashboard, navigate to `http://$MANCENTER_IP:8080` in a browser. | ||
|
|
||
| // RJS: Web browser? Or some Kubernetes browser? That looks like an environment variable, which won't work in a web browser? |
|
|
||
| // RJS: Web browser? Or some Kubernetes browser? That looks like an environment variable, which won't work in a web browser? | ||
|
|
||
| // RJS: What do these commands do? |
| You must xref:connect-outside-kubernetes.adoc[expose Hazelcast clusters outside Kubernetes] so you can connect external clients to them. | ||
|
|
||
| Learn how to xref:connect-outside-kubernetes.adoc[expose Hazelcast clusters outside Kubernetes] so you can connect external clients to them. | ||
| // RJS: Do you need to do this so MC can connect to the cluster too? |
| You can use the following command for the long format. | ||
| You can also see the status in YAML format: | ||
|
|
||
| // RJS: Does this provide more info or is it just a different format? |
|
|
||
| For example, if the older cluster was installed with the command `helm install hz hazelcast/hazelcast-enterprise`, the new CR name must be `hz-hazelcast-enterprise`. This means that PVCs created by the Helm Chart will attach to the pods created by Operator correctly. | ||
|
|
||
| // RJS: This is contradictory - hz-hazelcast-enterprise does not match the format name-hazelcast-persistence! |
| clusterSize: 5 | ||
| ---- | ||
| // RJS: How do you apply YAML config changes? |
| kubectl scale hazelcast hazelcast-sample --replicas 5 | ||
| ---- | ||
| // RJS: How do you verify it's worked? What's the behavior / service interruption when you scale up/down? No newline at end of file |
| | 5.16 | 5.6.0 | ||
| |=== | ||
|
|
||
| // RJS: Can we trim some older versions? Do we still provide images for them? Maybe we could just list the Platform version in the Operator release notes instead? |
| include::ROOT:example$/hazelcast.yaml[] | ||
| ---- | ||
|
|
||
| // RJS: How do you verify it's worked? What's the behavior / service interruption during upgrade? No newline at end of file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial copy edit of full docs set.