apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53181"
    uid: 7815e266-7f01-4a17-a7e8-dfdcf3bb8cb1
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 1.272627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 1.10336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 932.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 1.160379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 1.373564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:47:57Z"
    - latency: 994.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:46:57Z"
    - latency: 889.791µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:45:57Z"
    - latency: 1.29103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:44:57Z"
    - latency: 1.213784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:43:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53183"
    uid: a89e6e71-5e8e-4b7b-9793-fc652cfff086
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:34:57Z"
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.569287ms
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 8.617923ms
      message: 'load-balancer-api-external: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 4.504907ms
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 10.513221ms
      message: 'load-balancer-api-external: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 4.843664ms
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 9.579498ms
      message: 'load-balancer-api-external: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 5.006358ms
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 9.726855ms
      message: 'load-balancer-api-external: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 8.492323ms
      message: 'load-balancer-api-external: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 10.659765ms
      message: 'load-balancer-api-external: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:48:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53182"
    uid: 0878d262-fcb9-47a2-a78e-1fc66991d92c
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:34:57Z"
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.383623ms
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 8.650346ms
      message: 'load-balancer-api-internal: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 4.481657ms
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 10.576677ms
      message: 'load-balancer-api-internal: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 4.177809ms
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 9.61571ms
      message: 'load-balancer-api-internal: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 4.987287ms
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 9.733079ms
      message: 'load-balancer-api-internal: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 8.502782ms
      message: 'load-balancer-api-internal: tcp connection to ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 10.697766ms
      message: 'load-balancer-api-internal: resolved host name ab8cd9e0c318345e7b45130f970fb9c1-5411b4f85c2dd32a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:48:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-133-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53178"
    uid: de95c693-9d93-4886-8895-72d5dab46b9d
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:57Z"
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.620182ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 2.312949ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 2.848843ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 2.137319ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 2.376656ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 2.039213ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:47:57Z"
    - latency: 2.250917ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:46:57Z"
    - latency: 2.205012ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:45:57Z"
    - latency: 2.077257ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:44:57Z"
    - latency: 2.116952ms
      message: 'network-check-target-ip-10-0-133-123: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:43:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-138-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53177"
    uid: 804620d2-f023-4f20-8bd6-2f036060f3e1
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:57Z"
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.043µs
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 1.085473ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 1.848754ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 1.169745ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 1.005968ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 801.112µs
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:47:57Z"
    - latency: 1.069909ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:46:57Z"
    - latency: 986.593µs
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:45:57Z"
    - latency: 737.013µs
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:44:57Z"
    - latency: 1.23481ms
      message: 'network-check-target-ip-10-0-138-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:43:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-network-check-target-ip-10-0-138-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53179"
    uid: 3e5d06e3-99a4-4c3f-8f69-a89e4101cad8
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:35:57Z"
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.745699ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 2.762581ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 2.329746ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 2.229072ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 2.216291ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 1.961008ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:47:57Z"
    - latency: 2.247638ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:46:57Z"
    - latency: 2.2015ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:45:57Z"
    - latency: 2.026238ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:44:57Z"
    - latency: 2.139812ms
      message: 'network-check-target-ip-10-0-138-153: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:43:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T01:28:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-146.ec2.internal
      uid: da3a2006-2756-4497-a920-e581ba7a8fd8
    resourceVersion: "53180"
    uid: 28c3a942-aadf-4396-abdd-0d82b01b45c9
  spec:
    sourcePod: network-check-source-7d88cb55d8-jnxqv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T01:34:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.259452ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 2.023816ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:52:57Z"
    - latency: 1.16768ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 2.211579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:51:57Z"
    - latency: 949.276µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 2.082621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:50:57Z"
    - latency: 1.051686ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 2.152316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:49:57Z"
    - latency: 1.347888ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T02:48:57Z"
    - latency: 2.287952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T02:48:57Z"
kind: List
metadata:
  resourceVersion: ""