IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

We aim to streamline and simplify our automated management of GKE Gateways and Load Balancers. Specifically, we want to eliminate the need for complex JSON parsing of the 'description' field to extract critical filtering information. Our goal is to have this data directly available as individual labels for efficient CLI-based automation.

How this might work:

Modify the GKE Gateway and Load Balancer creation process to automatically populate relevant labels with the necessary filtering information. Instead of embedding this data in a JSON string within the 'description' field, populate labels such as 'k8sResource', 'k8sCluster', 'k8sNamespace', and 'k8sGateway' directly. This would allow for simple and direct access to these values using CLI commands without the need for additional JSON processing.

If applicable, reasons why alternative solutions are not sufficient:

Manual JSON Parsing:

While scripting can extract the JSON, it adds significant overhead, increases script complexity, and makes maintenance difficult. It also adds unneeded steps to any automated process.

External Data Stores:

Storing this information in an external database or configuration file adds another layer of complexity and potential failure points. It also requires additional synchronization and management overhead.

Current Label Usage:

Currently, the labels that are populated are missing the vital information that is contained within the JSON string. The label population is incomplete, and therefore insufficient.

Other information (workarounds you have tried, documentation consulted, etc):

We have attempted to work around this issue by developing scripts that parse the JSON string from the 'description' field. However, this approach is not scalable and significantly increases the complexity of our automation workflows.

We have consulted the official Google Cloud documentation for GKE Gateways and Load Balancers, but we have not found any recommended solutions for directly accessing this filtering information as individual labels.

Current Behavior:

{
    "IPAddress":"999.999.999.999",
    "IPProtocol":"TCP",
    "creationTimestamp":"2024-12-12T02:22:41.769-08:00",
    "description":"{\"k8sResource\":\"/namespaces/gateway/gateways/office-gateway\",\"k8sCluster\":\"/projects/999999999999/locations/asia-northeast3/clusters/sample-cluster\"}",
    "fingerprint":"xxxxxxx=",
    "id":"2266375990912425118",
    "kind":"compute#forwardingRule",
    "labelFingerprint":"xxxxxxxxx=",
    "labels":{
        "goog-gke-node":""
    },
    "loadBalancingScheme":"EXTERNAL_MANAGED",
    "name":"gkegw1-cpxx-gateway-office-gateway-hashxxxxx",
    "networkTier":"PREMIUM",
    "portRange":"80-80",
    "selfLink":"projects/sample-project/global/forwardingRules/gkegw-cpxx-gateway-office-gateway-hash1xxxxx",
    "target":"projects/sample-project/global/targetHttpProxies/gkegw-cpxx-gateway-office-gateway-hash2xxxxx"
}

Expected Behavior:

{
    "IPAddress":"999.999.999.999",
    "IPProtocol":"TCP",
    "creationTimestamp":"2024-12-12T02:22:41.769-08:00",
    "description":"{\"k8sResource\":\"/namespaces/gateway/gateways/office-gateway\",\"k8sCluster\":\"/projects/999999999999/locations/asia-northeast3/clusters/sample-cluster\"}",
    "fingerprint":"xxxxxxx=",
    "id":"2266375990912425118",
    "kind":"compute#forwardingRule",
    "labelFingerprint":"xxxxxxxxx=",
    "labels":{
        "goog-gke-node":"",
        "k8sResource":"/namespaces/gateway/gateways/office-gateway",
        "k8sNamespace":"gateway",
        "k8sGateway":"office-gateway",
        "k8sCluster":"/projects/999999999999/locations/asia-northeast3/clusters/sample-cluster"
    },
    "loadBalancingScheme":"EXTERNAL_MANAGED",
    "name":"gkegw1-cpxx-gateway-office-gateway-hashxxxxx",
    "networkTier":"PREMIUM",
    "portRange":"80-80",
    "selfLink":"projects/sample-project/global/forwardingRules/gkegw-cpxx-gateway-office-gateway-hash1xxxxx",
    "target":"projects/sample-project/global/targetHttpProxies/gkegw-cpxx-gateway-office-gateway-hash2xxxxx"
}