Docs: Feedback for Deploy a Cluster with the Hazelcast Platform Operator for Kubernetes #175
Comments
|
Hi @avtarraikmo, Actually, we request users to create CR YAML for both deployments. Am I missing something? EE
OS
|
hasancelik
pushed a commit
that referenced
this issue
Aug 29, 2024
…prise.yaml (#233) Now that operator is enterprise only, we should only reference `hazelcast-enterprise.yaml` as the file containing the Hazelcast Custom Resource Definitions. Steps 2.2 & 2.3 already reference `hazelcast-enterprise.yaml` for creating the Hazelcast cluster. As shown in #175 previously Step 2 contained two tabs (Open Source) and (Enterprise) with the Open Source steps using `hazelcast.yaml` and Enterprise using `hazelcast-enterprise.yaml`. The Open Source tab has been removed so we can remove all references to `hazelcast.yaml`
|
@hasancelik I believe this issue can be closed now, wdyt? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I have some feedback about this page
In Step 2 - we ask users to create hazelcast.yaml.
In the Open Source example, this is fine.
In the Enterprise example, this breaks as we ask for:
kubectl apply -f hazelcast-enterprise.yaml
Can we be consistent? Either use hazelcast.yaml everywhere - or ensure it's clear that there is need for one or the other?
The text was updated successfully, but these errors were encountered: