apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "71692"
    uid: 0074fd91-83c5-49a0-8b0e-3a97faf0bac7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:55:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.165731ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:37:55Z"
    - latency: 1.056568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 1.563255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 1.214063ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 1.215719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 1.066524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 1.014005ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:31:55Z"
    - latency: 1.36112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:30:55Z"
    - latency: 1.290057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:29:55Z"
    - latency: 1.10287ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:28:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "70360"
    uid: 3ab79a04-6aaa-49cf-8208-88684b19645f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:54:55Z"
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.503319ms
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 9.502753ms
      message: 'load-balancer-api-external: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 4.022482ms
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 9.079326ms
      message: 'load-balancer-api-external: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 3.629623ms
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 9.450719ms
      message: 'load-balancer-api-external: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 5.113024ms
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 8.216691ms
      message: 'load-balancer-api-external: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 3.928686ms
      message: 'load-balancer-api-external: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 11.974895ms
      message: 'load-balancer-api-external: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "70361"
    uid: 04360bee-67ce-42c5-bd73-66294d86dbde
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:54:55Z"
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.512575ms
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 9.484781ms
      message: 'load-balancer-api-internal: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 4.480442ms
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 9.025218ms
      message: 'load-balancer-api-internal: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 3.730938ms
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 9.413071ms
      message: 'load-balancer-api-internal: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 5.159877ms
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 8.144365ms
      message: 'load-balancer-api-internal: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 3.940724ms
      message: 'load-balancer-api-internal: tcp connection to a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 11.946433ms
      message: 'load-balancer-api-internal: resolved host name a108434221282469ea0d3e5c51ab3663-86aa7f9259dba86e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:32:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-network-check-target-ip-10-0-136-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "71689"
    uid: 3c63f063-80b2-416f-b326-c57808e4b7d7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:55:55Z"
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055162ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:37:55Z"
    - latency: 1.082103ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 1.202729ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 948.56µs
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 1.003838ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 829.651µs
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 1.08078ms
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:31:55Z"
    - latency: 802.698µs
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:30:55Z"
    - latency: 832.807µs
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:29:55Z"
    - latency: 919.284µs
      message: 'network-check-target-ip-10-0-136-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:28:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-network-check-target-ip-10-0-140-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "71690"
    uid: c23fa726-17bd-4626-9393-8ed722a77620
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:55:55Z"
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.466721ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:37:55Z"
    - latency: 2.007109ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 2.340177ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 2.583589ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 2.478997ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 2.194835ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 2.389021ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:31:55Z"
    - latency: 1.726245ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:30:55Z"
    - latency: 2.290419ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:29:55Z"
    - latency: 2.469452ms
      message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:28:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-network-check-target-ip-10-0-142-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "71691"
    uid: 3cc3006c-d57d-484f-95a1-37cf766ed91f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:55:55Z"
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.464137ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:37:55Z"
    - latency: 2.291641ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 2.103298ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 2.416209ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 2.093845ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 2.064948ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 2.108921ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:31:55Z"
    - latency: 1.955028ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:30:55Z"
    - latency: 2.422174ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:29:55Z"
    - latency: 2.416861ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:28:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T05:48:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-88-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-88.ec2.internal
      uid: 50da1b68-678a-4c12-a30b-67622bf755f5
    resourceVersion: "70359"
    uid: d80312f9-e0b8-4b16-a005-40c49dd856f7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-jhllr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T05:54:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.671µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 2.046965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:36:55Z"
    - latency: 875.042µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 2.182812ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:35:55Z"
    - latency: 1.339305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 1.909306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:34:55Z"
    - latency: 1.010789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 1.794458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:33:55Z"
    - latency: 862.236µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T06:32:55Z"
    - latency: 1.936954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T06:32:55Z"
kind: List
metadata:
  resourceVersion: ""