Merge pull request #13 from danehans/rr_lb_docs

Adds docs for load balance annoation

Author: danehans

pkg/i2gw/implementations/kgateway/README.md

@@ -62,7 +62,9 @@ The command should generate Gateway API and Kgateway resources.
 
 ### Backend Behavior
 
-- `nginx.ingress.kubernetes.io/proxy-connect-timeout`
+- `nginx.ingress.kubernetes.io/proxy-connect-timeout`: Sets the timeout for establishing a connection with a proxied server. It should be noted that this timeout
+  cannot usually exceed 75 seconds.
+- `nginx.ingress.kubernetes.io/load-balance`: Sets the algorithm to use for load balancing to a proxied server. The only supported value is `round_robin`.
 - `nginx.ingress.kubernetes.io/affinity`: Enables session affinity (only "cookie" type is supported). Maps to `BackendConfigPolicy.spec.loadBalancer.ringHash.hashPolicies`.
 - `nginx.ingress.kubernetes.io/session-cookie-name`: Specifies the name of the cookie used for session affinity. Maps to `BackendConfigPolicy.spec.loadBalancer.ringHash.hashPolicies[].cookie.name`.
 - `nginx.ingress.kubernetes.io/session-cookie-path`: Defines the path that will be set on the cookie. Maps to `BackendConfigPolicy.spec.loadBalancer.ringHash.hashPolicies[].cookie.path`.

pkg/i2gw/providers/ingressnginx/README.md

@@ -83,7 +83,10 @@ The ingress-nginx provider currently supports translating the following annotati
 
 ### Backend (Upstream) Configuration
 
-- `nginx.ingress.kubernetes.io/proxy-connect-timeout`: Controls the upstream connection timeout. For the Kgateway implementation, this maps to `BackendConfigPolicy.spec.connectTimeout`.
+- `nginx.ingress.kubernetes.io/proxy-connect-timeout`: Controls the upstream connection timeout. For the Kgateway implementation,
+  this maps to `BackendConfigPolicy.spec.connectTimeout`.
+- `nginx.ingress.kubernetes.io/load-balance`: Sets the algorithm to use for load balancing. The only supported value is `round_robin`.
+  For the Kgateway implementation, this maps to `BackendConfigPolicy.spec.loadBalancer`.
 
 **Note:** For the Kgateway implementation, if multiple Ingress resources reference the same Service with different `proxy-connect-timeout` values, ingress2gateway will emit warnings because Kgateway cannot safely apply multiple conflicting `BackendConfigPolicy` resources to the same Service.