apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "53291"
    uid: c92e5e68-eaa6-4d55-8fe6-efec88e2702b
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:38:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.72864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 960.459µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 947.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 1.04969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:56:16Z"
    - latency: 1.031791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:55:16Z"
    - latency: 1.518758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:54:16Z"
    - latency: 962.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:16Z"
    - latency: 1.330767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:16Z"
    - latency: 1.292686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:16Z"
    - latency: 1.199165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "54791"
    uid: 32268e8d-b840-44da-aae6-28ab59a34817
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:37:16Z"
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.376587ms
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 7.622892ms
      message: 'load-balancer-api-external: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 4.098836ms
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 9.133892ms
      message: 'load-balancer-api-external: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 4.364883ms
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 8.893074ms
      message: 'load-balancer-api-external: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 5.156602ms
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 8.054978ms
      message: 'load-balancer-api-external: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 5.179426ms
      message: 'load-balancer-api-external: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 11.201454ms
      message: 'load-balancer-api-external: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:57:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "54790"
    uid: 1a847b36-745f-488f-a7c3-f16269e9e5db
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:37:16Z"
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.87326ms
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 7.699491ms
      message: 'load-balancer-api-internal: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 4.079272ms
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 9.23793ms
      message: 'load-balancer-api-internal: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 4.360125ms
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 8.940241ms
      message: 'load-balancer-api-internal: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 4.859313ms
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 8.083995ms
      message: 'load-balancer-api-internal: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 10.422413ms
      message: 'load-balancer-api-internal: tcp connection to ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 11.2952ms
      message: 'load-balancer-api-internal: resolved host name ade452e91310c42c49fc202922b37da9-4414264817ffc2ce.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:57:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-133-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "53288"
    uid: c399d309-2083-4df8-a465-f81d32670fc4
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:38:16Z"
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.026µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 1.215595ms
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 1.044413ms
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 822.066µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:56:16Z"
    - latency: 1.081465ms
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:55:16Z"
    - latency: 877.737µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:54:16Z"
    - latency: 963.242µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:16Z"
    - latency: 991.451µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:16Z"
    - latency: 956.305µs
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:16Z"
    - latency: 1.027945ms
      message: 'network-check-target-ip-10-0-133-121: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-140-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "53289"
    uid: b3727ed9-fd17-4b06-b47c-fabd4ecb927c
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:38:16Z"
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452986ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 2.247595ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 2.497265ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 2.534829ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:56:16Z"
    - latency: 2.568658ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:55:16Z"
    - latency: 2.191937ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:54:16Z"
    - latency: 2.356755ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:16Z"
    - latency: 2.443689ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:16Z"
    - latency: 2.320492ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:16Z"
    - latency: 2.758109ms
      message: 'network-check-target-ip-10-0-140-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-network-check-target-ip-10-0-143-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "53290"
    uid: 84247de4-82b3-4e7f-9eeb-62f0adb56415
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:38:16Z"
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.339866ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 2.525854ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 2.418118ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 2.335505ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:56:16Z"
    - latency: 1.994492ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:55:16Z"
    - latency: 1.982883ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:54:16Z"
    - latency: 2.023906ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:53:16Z"
    - latency: 2.424695ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:52:16Z"
    - latency: 2.513067ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:51:16Z"
    - latency: 2.103436ms
      message: 'network-check-target-ip-10-0-143-248: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:50:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:31:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-121.ec2.internal
      uid: 0315b4bf-1261-4f39-9e8a-f39254f8282f
    resourceVersion: "54789"
    uid: 7e413faa-ffe9-4356-afcc-62b55ae6d31b
  spec:
    sourcePod: network-check-source-6f8b768455-rzxhs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:37:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 853.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 1.727206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:01:16Z"
    - latency: 1.09016ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 2.227445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:00:16Z"
    - latency: 883.728µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 2.009198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:59:16Z"
    - latency: 949.717µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 1.786818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:58:16Z"
    - latency: 901.032µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T12:57:16Z"
    - latency: 1.84446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T12:57:16Z"
kind: List
metadata:
  resourceVersion: ""