apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "54669"
    uid: 14a8b88c-cb95-416c-b6d4-895233161553
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:24:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 953.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 1.061755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 970.203µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 1.497932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:48:51Z"
    - latency: 963.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:47:51Z"
    - latency: 1.722268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:46:51Z"
    - latency: 1.095048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:45:51Z"
    - latency: 1.280128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:44:51Z"
    - latency: 1.75856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:43:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "55731"
    uid: 0e6d4681-38d0-4755-8d30-6507c2157f5f
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:23:51Z"
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.590707ms
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 6.606172ms
      message: 'load-balancer-api-external: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 4.643569ms
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 6.895425ms
      message: 'load-balancer-api-external: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 4.857424ms
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 6.768763ms
      message: 'load-balancer-api-external: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 4.638373ms
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 6.730068ms
      message: 'load-balancer-api-external: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 3.422602ms
      message: 'load-balancer-api-external: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 7.034535ms
      message: 'load-balancer-api-external: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:49:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "55732"
    uid: a0909952-2c52-4413-9ed3-5f422e9d536b
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:23:51Z"
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.566167ms
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 6.640376ms
      message: 'load-balancer-api-internal: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 4.652603ms
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 6.851055ms
      message: 'load-balancer-api-internal: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 4.194341ms
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 6.811355ms
      message: 'load-balancer-api-internal: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 3.727713ms
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 6.669369ms
      message: 'load-balancer-api-internal: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 3.411691ms
      message: 'load-balancer-api-internal: tcp connection to a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 7.086338ms
      message: 'load-balancer-api-internal: resolved host name a42eff592d32b40c986928542716bf59-2c25027cddf6835c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:49:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-network-check-target-ip-10-0-128-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "54667"
    uid: 6f3b2ea6-8b4c-4236-8a34-7ce671bd8e5a
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:24:51Z"
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.241029ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 2.066298ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 2.062283ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 1.805426ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 1.999882ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:48:51Z"
    - latency: 1.711442ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:47:51Z"
    - latency: 1.891988ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:46:51Z"
    - latency: 1.886135ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:45:51Z"
    - latency: 1.946235ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:44:51Z"
    - latency: 2.147515ms
      message: 'network-check-target-ip-10-0-128-159: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:43:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-network-check-target-ip-10-0-128-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "54666"
    uid: 558f5125-c1f0-4fe9-b055-835798bae9a1
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:24:51Z"
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.062405ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 1.195255ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 805.169µs
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 1.120914ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 1.165097ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:48:51Z"
    - latency: 1.693315ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:47:51Z"
    - latency: 935.997µs
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:46:51Z"
    - latency: 976.911µs
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:45:51Z"
    - latency: 1.613215ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:44:51Z"
    - latency: 1.304487ms
      message: 'network-check-target-ip-10-0-128-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:43:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-network-check-target-ip-10-0-142-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "54668"
    uid: d2dd8ba9-b634-414b-bb6c-3d0031e2a221
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:24:51Z"
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305158ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 2.270584ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 2.21991ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 2.184048ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 2.351699ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:48:51Z"
    - latency: 2.36992ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:47:51Z"
    - latency: 1.997476ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:46:51Z"
    - latency: 2.328764ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:45:51Z"
    - latency: 2.535304ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:44:51Z"
    - latency: 2.33316ms
      message: 'network-check-target-ip-10-0-142-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:43:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T22:17:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-229-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-229.ec2.internal
      uid: 75dc0d57-703b-49b4-ad74-f48a2d2b9b38
    resourceVersion: "55730"
    uid: 0362dd50-fc89-4338-b0b7-41acf3c9c8f3
  spec:
    sourcePod: network-check-source-989f8b8dc-kmn4d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T22:23:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 1.625133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:53:51Z"
    - latency: 1.073864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 1.687915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:52:51Z"
    - latency: 890.602µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 1.965065ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:51:51Z"
    - latency: 937.065µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 1.684763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:50:51Z"
    - latency: 1.204285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T22:49:51Z"
    - latency: 1.915436ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T22:49:51Z"
kind: List
metadata:
  resourceVersion: ""