apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "21855"
    uid: fc716500-1168-4bb0-8710-4ac4c5cea712
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:49:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:10:13Z"
    - latency: 793.341µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:09:13Z"
    - latency: 1.129834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:08:13Z"
    - latency: 840.959µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:07:13Z"
    - latency: 769.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 1.903038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 805.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 1.050003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 827.428µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 1.116829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:01:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "20233"
    uid: 573339b9-90df-455b-a035-fef18e3b7018
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:48:13Z"
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.244822ms
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 8.927334ms
      message: 'load-balancer-api-external: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 5.955272ms
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 11.601801ms
      message: 'load-balancer-api-external: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 8.495357ms
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 9.627537ms
      message: 'load-balancer-api-external: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 4.825251ms
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 9.746209ms
      message: 'load-balancer-api-external: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 5.850368ms
      message: 'load-balancer-api-external: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 8.798885ms
      message: 'load-balancer-api-external: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:02:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "20232"
    uid: 23fea3c4-3d57-47ce-ae27-08ed8d0dd3fe
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:48:13Z"
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.053206ms
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 8.978524ms
      message: 'load-balancer-api-internal: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 5.972152ms
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 11.795243ms
      message: 'load-balancer-api-internal: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 8.465924ms
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 9.675088ms
      message: 'load-balancer-api-internal: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 4.847691ms
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 9.826855ms
      message: 'load-balancer-api-internal: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 5.787236ms
      message: 'load-balancer-api-internal: tcp connection to a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 8.918053ms
      message: 'load-balancer-api-internal: resolved host name a6baee18bbba24cf096c5374b98e19d2-2b611050d978fc64.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:02:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-network-check-target-ip-10-0-130-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "21854"
    uid: 9f1f6696-1cda-4823-8189-3b33027566df
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:49:13Z"
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133019ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:10:13Z"
    - latency: 1.955808ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:09:13Z"
    - latency: 2.06371ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:08:13Z"
    - latency: 2.151623ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:07:13Z"
    - latency: 1.966048ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 3.393063ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 2.108075ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 2.314611ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 1.781176ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 1.998894ms
      message: 'network-check-target-ip-10-0-130-219: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:01:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-network-check-target-ip-10-0-140-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "21853"
    uid: 8a51ce05-2afe-4184-b2e9-0e5d4d58b376
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:49:13Z"
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381973ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:10:13Z"
    - latency: 2.329519ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:09:13Z"
    - latency: 2.370099ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:08:13Z"
    - latency: 2.212265ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:07:13Z"
    - latency: 2.366533ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 3.105674ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 1.911218ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 2.378687ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 2.560619ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 2.286606ms
      message: 'network-check-target-ip-10-0-140-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:01:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-network-check-target-ip-10-0-140-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "21852"
    uid: 39d83a7a-d9d8-4b44-9dc6-d7c16e9e3c04
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:49:13Z"
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.088µs
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:10:13Z"
    - latency: 766.536µs
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:09:13Z"
    - latency: 1.230972ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:08:13Z"
    - latency: 1.225977ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:07:13Z"
    - latency: 871.16µs
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 2.190616ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 733.488µs
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 1.386493ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 1.308581ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 1.031565ms
      message: 'network-check-target-ip-10-0-140-196: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:01:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T11:42:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-196.ec2.internal
      uid: fae0647f-3708-4456-bbdb-ecda74b519cf
    resourceVersion: "20231"
    uid: 212b1ac4-8496-4b87-a337-d5ce204bc847
  spec:
    sourcePod: network-check-source-6f8b768455-bxwdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T11:48:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.168537ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 1.853124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:06:13Z"
    - latency: 931.726µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 2.269148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:05:13Z"
    - latency: 933.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 1.780034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:04:13Z"
    - latency: 1.045133ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 1.73704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:03:13Z"
    - latency: 892.507µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T12:02:13Z"
    - latency: 1.940677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T12:02:13Z"
kind: List
metadata:
  resourceVersion: ""