- The iptables mode of kube-proxy now tracks accepted packets that are destined for node-ports on localhost by introducing `kubeproxy_iptables_localhost_nodeports_accepted_packets_total` metric.

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this label type.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this label type was last updated.
     * Stored as a long value representing milliseconds since epoch.

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this role.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this role was last updated.
     * Stored as a long value representing milliseconds since epoch.

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this elevate word configuration.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this elevate word configuration was last updated.

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this request header configuration.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this request header configuration was last updated.

 * `CLEARTEXT` is an insecure configuration that is used for `http://` URLs.

These loosely follow the model set in [Google Cloud Policies](https://cloud.google.com/load-balancing/docs/ssl-policies-concepts). We [track changes](../security/tls_configuration_history.md) to this policy.

            // Verify that the rate limiter tracked some activity
            AuthenticationRateLimiter.RateLimiterStats stats = concurrentLimiter.getStats();
            assertTrue(stats.getActiveAccounts() > 0 || stats.getActiveIps() > 0, "Should have tracked some activity");
        } finally {
            concurrentLimiter.close();
        }
    }

    @Test

- A new kubelet metric `image_pull_duration_seconds` was added. The metric tracks the duration (in seconds) it takes for an image to be pulled, including the time spent in the waiting queue of image puller. The metric is broken down by bucketed image size. ([#121719](https://github.com/kubernetes/kubernetes/pull/121719), [@rui...

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this access token.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this access token was last updated.
     * Stored as a long value representing milliseconds since epoch.

     */
    @Required
    @Size(max = 1000)
    public String id;

    /**
     * The username of the user who last updated this bad word entry.
     * Used for audit trail purposes to track who made changes.
     */
    @Size(max = 1000)
    public String updatedBy;

    /**
     * The timestamp when this bad word entry was last updated.
     * Stored as a long value representing milliseconds since epoch.