Zookeeper configuration

Applies to: Kyvos Enterprise Kyvos Cloud (SaaS on AWS) Kyvos AWS Marketplace

Kyvos Azure Marketplace Kyvos GCP Marketplace Kyvos Single Node Installation (Kyvos SNI)

You can configure Zookeeper for cloud (AWS, GCP, and Azure) and on-prem deployments.

Note

You can see the last Zookeeper operation details, including progress status and start time, by clicking the i icon located next to the Revert button. To view more comprehensive details, simply click the View Details link, which will take you to the Operations page, where you can view the operation information in detail.

Point to know about Zookeeper ACL

Zookeeper ACL (Access Control List) can be enabled as a configurable option for added security. It is supported only for IP-based deployments with individual IPs or CIDR ranges.
- When to enable Zookeeper ACL:
  - If the Zookeeper subnet is openly accessible from other networks.
  - If multiple applications, including those from different vendors, are deployed in the same subnet.
    In these cases, enabling ACL adds an extra layer of security.
- When it’s less critical:
  - If the Zookeeper subnet is dedicated for Kyvos only.
  - If the subnet is isolated from other networks with very restricted access.
    In such cases, the security risk is minimal, and enabling ACL may not be mandatory.
All the cluster nodes will be included in the Zookeeper ACL, even if you have not explicitly specified them.
Zookeeper ACL can be enabled during the deployment of a managed Zookeeper. It can also be enabled or disabled independently in an existing managed Zookeeper environment, without requiring redeployment. In such cases, the logged operation name will be Configure Zookeeper ACL.
All cluster nodes, whether dedicated or Kubernetes, must be included in the node list for Zookeeper access, along with the subnets or IPs used for processing in the environment.
The list of cluster nodes implicitly granted Zookeeper access permissions will be clearly indicated on the Zookeeper page of Kyvos Manager.
Automatic updates:
- When new nodes are added to the cluster, they will automatically be added to the Zookeeper ACL list to ensure seamless access.
- When existing nodes are removed from the cluster, they will automatically be removed from the ACL list. This prevents any security loopholes by ensuring that released or deleted node IPs cannot connect to Zookeeper.

Configuring Zookeeper

To configure Zookeeper, follow these steps.

On the navigation pane, click Kyvos and Ecosystem > Zookeeper.
The Zookeeper page is displayed.
Enter the following details:

Configuring Zookeeper service

Hadoop/EMR Configuration page with the option for removing Zookeeper.

Click the Remove Zookeeper link and provide your Kyvos Manager Password to remove the Zookeeper.

Once the Zookeeper is removed, you will see the option to deploy it on the Hadoop/EMR page, as shown in the following figure.

Click the Deploy Zookeeper link and provide your Kyvos Manager Password to deploy the Zookeeper.
Click the Apply button from the top-right of the page.