Key (annotation) | Value sample | Type | Description |
---|---|---|---|
loadbalancer.gcorelabs.com/flavor | lb1-1-2 | String | Specifies a custom name for the flavor |
loadbalancer.gcorelabs.com/proxy-protocol | true | Boolean | Enables proxy protocol type for Load Balancer listeners |
loadbalancer.gcorelabs.com/x-forwarded-for | true | Boolean | Adds the “X-Forwarded-For,” “X-Forwarded-Port” and “X-Forwarded-Proto“ headers to requests |
Enhanced Logging and Monitoring | |||
loadbalancer.gcorelabs.com/logging-topic-name | topic-123 | String | Specifies LaaS topic name for pushing logs. Note: Must be used with the logging-destination-region-id |
loadbalancer.gcorelabs.com/logging-destination-region-id | 1 | Integer | Specifies LaaS destination region. Note: Must be used with the logging-topic-name |
loadbalancer.gcorelabs.com/logging-retention-policy-period | 45 | Integer | Configures log retention policy for LaaS topic (in days) |
loadbalancer.gcore.com/logging-retention-policy-period | 30 | Integer | Defines log retention policy for the LaaS topic (in days) |
loadbalancer.gcore.com/logging-topic-name | my-logs | String | Specifies the LaaS topic name for pushing logs |
loadbalancer.gcore.com/logging-destination-region-id | 15 | Integer | Defines the LaaS destination region for log storage |
Advanced DDoS Protection | |||
loadbalancer.gcorelabs.com/ddos-profile | { "profile_template":65, "fields": [{ "base_field":272, "field_value":40 }] } | Integer | Configures and ads the DDoS Protection profile to the Load Balancer |
loadbalancer.gcore.com/ddos-profile | { "profile_template":75, "fields": [{ "base_field":300, "field_value":50 }] } | String | Specifies an Advanced DDoS Protection profile using a JSON string |
Connection and Timeout Configurations | |||
loadbalancer.gcorelabs.com/timeout-client-data | 6000 | Integer | Sets client data timeouts for Load Balancer listeners (in msec). Note: When removed, the previously set value remains in effect |
loadbalancer.gcorelabs.com/timeout-member-connect | 6000 | Integer | Sets member connect timeouts for Load Balancer listeners (in msec). Note: When removed, the previously set value remains in effect |
loadbalancer.gcorelabs.com/timeout-member-data | 6000 | Integer | Sets member data timeouts for Load Balancer listeners (in msec). Note: When removed, the previously set value remains in effect |
loadbalancer.gcore.com/listener-connection-limit | 500 | Integer | Sets a limit on the number of concurrent connections per listener |
loadbalancer.gcore.com/listener-timeout-client-data | "30s" | String | Defines client data timeout duration (e.g., ”30s” or “1m”) |
loadbalancer.gcore.com/listener-timeout-member-connect | "30s" | String | Defines the connection timeout between Load Balancer and backend members |
loadbalancer.gcore.com/listener-timeout-member-data | "30s" | String | Defines the data transmission timeout between Load Balancer and backend members |
IP and Network Configurations | |||
loadbalancer.gcorelabs.com/floating-cleanup | true | Boolean | Automatically cleans up the floating IP assigned to the Load Balancer after deleting the service |
service.beta.kubernetes.io/gcore-internal-load-balancer | true | Boolean | Disables floating IP creation and makes the Load Balancer unavailable for external requests |
service.beta.kubernetes.io/gcore-external-load-balancer | true | Boolean | Makes the Load Balancer public |
loadbalancer.gcore.com/floating-ip | "1.1.1.1" | String | Specifies a floating IP for a private Load Balancer, only for internal networks |
loadbalancer.gcore.com/floating-ip | "192.168.1.10" | String | Assigns an existing floating IP address to the Load Balancer |
loadbalancer.gcore.com/floating-ip-cleanup | true | Boolean | Automatically removes the assigned floating IP when the Service is deleted |
loadbalancer.gcore.com/reserved-ip | "10.0.0.42" | String | Specifies a reserved IP for the Load Balancer |
loadbalancer.gcore.com/reserved-ip-cleanup | true | Boolean | Automatically cleans up reserved IPs upon deletion |
65
, 272
, and 40
), use the appropriate values for your project. The value format is the same as supported by the public DDoS Protection API.
To enable logging for your cluster, use the following one:
test123
and 15
), use the appropriate values for your project.