# How to Create a Pool in Kubernetes Load Balancer? To create a pool in Kubernetes load balancer, follow the steps given below: **Step 1:** [Login](https://customer.acecloudhosting.com/index.php?m=ace_product_register_addon\&action=login) to your account.
**Step 2:** Navigate to **Services** and then click on **My Services.**
**Step 3:** Click on your project.
**Step 4:** Navigate to **Kubernetes** and then click on **K8s Load Balancer**.
**Step 5:** Click on the load balancer name for which you want to create a pool.
**Step 6:** Go to **Listener** tab and click on the listener's name for which you want to create the pool.
**Step 7:** Click on the **Pools** tab and click on **Create Pool**.
**Step 8:** Enter **Pool Details** and click **Next.**
| **Field** | **Description** | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | Enter the name of the Pool. | | Description | Enter the description of the pool. | | Algorithm |

Select the load balancing algorithm for the pool from the below options:

  1. Least connections
  2. Round robin
  3. Source IP
| | TLS Enabled | | | TLS Cipher String | Enter List of ciphers in OpenSSL format and it should be colon-separated. | | Session Persistence |

Select a JSON object specifying the session persistence for the pool from the below options:

  1. HTTP Cookie
  2. APP Cookie
  3. Source IP
| | Cookie Name\* | Enter the name of the cookie to use for session persistence. | **Step 9:** Click on **Add** against the instance, you want to allocate as a member.
**Step 10:** Click on edit icon to enter the port number.
**Step 11:** Enter the **Port** number, click on save icon and press the **Next** button.
**Step 12:** Enter **Health Monitor** details and click **Create Pool.** **Note:** If you do not want to create **Monitor,** select **No** and click **Create Pool.**
| **Field** | **Description** | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name\* | Enter the name of the Health Monitor. | | Type\* |

Select a protocol for the health monitor from the below options:

  1. HTTP
  2. HTTPS
  3. PING
  4. TCP
  5. TLS-HELLO
  6. UDP-CONNECT
  7. SCTP
| | Max Retries Down\* | Enter the number of allowed check failures before changing the operating status of the member to ERROR. A valid value is from 1 to 10. The default is 3. | | Delay (sec)\* | Enter the interval, in seconds, between health checks. The default is 10. | | Max Retries\* | Enter the number of successful checks before changing the operating status of the member to ONLINE. The default is 1. | | Timeout (sec)\* | The time, in seconds, after which a health check times out. The default is 5. | | HTTP Method |

Select the HTTP method that the health monitor uses for requests from the below options:

  1. GET
  2. HEAD
  3. POST
  4. PUT
  5. DELETE
  6. TRACE
  7. OPTIONS
  8. PATCH
  9. CONNECT
| | Expected Codes | Enter the HTTP status codes expected in response from the member to declare it healthy. The default is 200. | | URL Path | Enter the HTTP URL path of the request sent by the monitor to test the health of a member. Must be a string that begins with a forward slash. The default URL path is /. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.acecloud.ai/knowledge-base/kubernetes/how-to-create-a-pool-in-kubernetes-load-balancer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.