apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "60511"
    uid: 0dd462e8-7b07-49bb-adb9-803833ab626c
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:19:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.166765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 935.267µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 1.209684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 1.474416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:35Z"
    - latency: 906.831µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:35Z"
    - latency: 1.047692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:35Z"
    - latency: 1.261133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:35Z"
    - latency: 1.284674ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:35Z"
    - latency: 1.280682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:35Z"
    - latency: 1.371888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "62292"
    uid: a9926c5a-977e-4d2d-b517-3762af26aa45
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:18:35Z"
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.702883ms
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 8.073021ms
      message: 'load-balancer-api-external: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 4.77061ms
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 6.321697ms
      message: 'load-balancer-api-external: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 4.085565ms
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 7.279577ms
      message: 'load-balancer-api-external: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 4.731406ms
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 8.723537ms
      message: 'load-balancer-api-external: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 5.082495ms
      message: 'load-balancer-api-external: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 8.842251ms
      message: 'load-balancer-api-external: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:38:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "62291"
    uid: 12b3bd81-84c1-4e8f-9eb8-626f729126f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:18:35Z"
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.686919ms
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 8.104029ms
      message: 'load-balancer-api-internal: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 4.822246ms
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 6.207785ms
      message: 'load-balancer-api-internal: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 4.114014ms
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 7.261664ms
      message: 'load-balancer-api-internal: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 4.709003ms
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 8.750869ms
      message: 'load-balancer-api-internal: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 5.054985ms
      message: 'load-balancer-api-internal: tcp connection to adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 8.918274ms
      message: 'load-balancer-api-internal: resolved host name adc3b2268a78347bfbcda2ec9b93daac-db80a6e3334ba337.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:38:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-network-check-target-ip-10-0-137-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "60508"
    uid: ee3733f1-3591-4de1-af9a-c2e8825c2ac9
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:19:35Z"
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.114662ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 1.818654ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 2.477463ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 2.240404ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:35Z"
    - latency: 2.390116ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:35Z"
    - latency: 2.018551ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:35Z"
    - latency: 2.458942ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:35Z"
    - latency: 1.888892ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:35Z"
    - latency: 2.22635ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:35Z"
    - latency: 2.121395ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-network-check-target-ip-10-0-143-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "60507"
    uid: e2d59920-c165-47ee-9fe5-a14c755e04dd
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:19:35Z"
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169057ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 860.193µs
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 1.288178ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 1.071014ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:35Z"
    - latency: 1.019565ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:35Z"
    - latency: 941.984µs
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:35Z"
    - latency: 1.028807ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:35Z"
    - latency: 1.012547ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:35Z"
    - latency: 1.1444ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:35Z"
    - latency: 1.08325ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-network-check-target-ip-10-0-143-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "60509"
    uid: 1b1212c1-a36a-4d80-94e7-23235894b9f0
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:19:35Z"
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.202699ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 2.338065ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 2.895746ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 2.378402ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:37:35Z"
    - latency: 2.462522ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:36:35Z"
    - latency: 2.677061ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:35:35Z"
    - latency: 2.784499ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:34:35Z"
    - latency: 2.39672ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:33:35Z"
    - latency: 2.294365ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:32:35Z"
    - latency: 2.84423ms
      message: 'network-check-target-ip-10-0-143-82: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:31:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T23:12:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-250-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-250.ec2.internal
      uid: 6700ec37-d448-4901-bae8-3dfc6a66674e
    resourceVersion: "62290"
    uid: 1f23bc29-821d-4849-9cb6-5a30ab79713f
  spec:
    sourcePod: network-check-source-7cbc45fddc-v4qgc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T23:18:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.26µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 1.650595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:42:35Z"
    - latency: 956.145µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 1.77733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:41:35Z"
    - latency: 909.699µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 1.525102ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:40:35Z"
    - latency: 878.849µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 2.263369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:39:35Z"
    - latency: 1.047414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T23:38:35Z"
    - latency: 1.907464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T23:38:35Z"
kind: List
metadata:
  resourceVersion: ""