apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "68156"
    uid: 40ac554f-3da2-4ffa-a511-56ee2c8a270a
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:28:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 884.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 1.48148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 845.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 1.152614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:32Z"
    - latency: 1.236927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:32Z"
    - latency: 1.535478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:32Z"
    - latency: 837.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:32Z"
    - latency: 1.894612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:32Z"
    - latency: 881.874µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "69003"
    uid: 7d45bf52-6b6b-4cd8-a1c8-fb67d3f83cd9
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:27:32Z"
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.405381ms
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 9.355945ms
      message: 'load-balancer-api-external: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 3.531986ms
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 9.146103ms
      message: 'load-balancer-api-external: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 5.58372ms
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 8.312423ms
      message: 'load-balancer-api-external: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 5.058313ms
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 11.136344ms
      message: 'load-balancer-api-external: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 4.427744ms
      message: 'load-balancer-api-external: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 6.337356ms
      message: 'load-balancer-api-external: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "69002"
    uid: a507d076-15af-47d9-a22a-8548f56fa3be
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:27:32Z"
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.35627ms
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 9.411655ms
      message: 'load-balancer-api-internal: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 3.57244ms
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 9.227102ms
      message: 'load-balancer-api-internal: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 4.597333ms
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 8.393327ms
      message: 'load-balancer-api-internal: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 3.349216ms
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 11.223057ms
      message: 'load-balancer-api-internal: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 4.415961ms
      message: 'load-balancer-api-internal: tcp connection to a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 6.425411ms
      message: 'load-balancer-api-internal: resolved host name a3a90b71523a5454b892e494ac567b4f-c0b3d5e3800c4705.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-133-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "68154"
    uid: f551e43d-5662-4789-85d1-1184f24fd29e
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:28:32Z"
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.521086ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 2.409884ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 2.782151ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 2.300622ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 2.459339ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:32Z"
    - latency: 2.773844ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:32Z"
    - latency: 3.470719ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:32Z"
    - latency: 2.387278ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:32Z"
    - latency: 2.586963ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:32Z"
    - latency: 2.462386ms
      message: 'network-check-target-ip-10-0-133-252: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-140-51
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "68153"
    uid: edf43a2e-ae89-45ee-a0c2-f6220ef6b06b
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:28:32Z"
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.803µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 850.069µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 990.716µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 830.799µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 1.000328ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:32Z"
    - latency: 922.379µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:32Z"
    - latency: 931.546µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:32Z"
    - latency: 1.217867ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:32Z"
    - latency: 984.974µs
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:32Z"
    - latency: 1.087175ms
      message: 'network-check-target-ip-10-0-140-51: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-ip-10-0-141-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "68155"
    uid: 7f895686-e9b6-453b-8313-727e890839f3
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:28:32Z"
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.515183ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 2.371893ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 2.409588ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 2.483012ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 2.379459ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:52:32Z"
    - latency: 2.637676ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:51:32Z"
    - latency: 3.950204ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:50:32Z"
    - latency: 2.54331ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:49:32Z"
    - latency: 2.486772ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:48:32Z"
    - latency: 2.426974ms
      message: 'network-check-target-ip-10-0-141-139: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:47:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:21:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-51-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-51.ec2.internal
      uid: 3c67b072-0138-4635-9820-0aec21cca01b
    resourceVersion: "69001"
    uid: 20f036c5-ec79-40a4-b682-0a6665952e4f
  spec:
    sourcePod: network-check-source-6f8b768455-ltwfd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T17:27:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 1.673373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:57:32Z"
    - latency: 848.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 2.014321ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:56:32Z"
    - latency: 880.877µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 1.748325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:55:32Z"
    - latency: 1.050989ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 1.777807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:54:32Z"
    - latency: 942.689µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:53:32Z"
    - latency: 1.879648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:53:32Z"
kind: List
metadata:
  resourceVersion: ""