apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "33455"
    uid: f6f8fae8-b718-47fb-b134-6a8b93e9b1bd
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 842.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 1.438281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 1.182565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 1.014107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 1.056637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 974.394µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 985.4µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 1.081401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:06Z"
    - latency: 997.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:06Z"
    - latency: 999.04µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "32584"
    uid: f875db90-dab6-46c0-b74a-ecf53189444a
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.708409ms
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 7.947267ms
      message: 'load-balancer-api-external: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 6.871639ms
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 8.138132ms
      message: 'load-balancer-api-external: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 4.23296ms
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 7.600546ms
      message: 'load-balancer-api-external: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 4.688008ms
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 8.767714ms
      message: 'load-balancer-api-external: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 3.735222ms
      message: 'load-balancer-api-external: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 8.101803ms
      message: 'load-balancer-api-external: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "32585"
    uid: 7c610c51-647d-4819-b017-489edbbd65cf
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.675447ms
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 7.986389ms
      message: 'load-balancer-api-internal: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 6.857882ms
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 8.230702ms
      message: 'load-balancer-api-internal: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 4.987732ms
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 7.651845ms
      message: 'load-balancer-api-internal: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 4.68512ms
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 8.830974ms
      message: 'load-balancer-api-internal: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 4.523099ms
      message: 'load-balancer-api-internal: tcp connection to ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 8.139898ms
      message: 'load-balancer-api-internal: resolved host name ab8cbaa99977d481491ca6c10d7576da-0d40256820b0172f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:21:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-129-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "33453"
    uid: d138de9e-02e6-4ffb-ad27-dbbece2a682f
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:06Z"
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.300475ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 1.228997ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 1.429151ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 1.444649ms
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 887.993µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 968.846µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 984.727µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 849.856µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:06Z"
    - latency: 850.313µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:06Z"
    - latency: 843.427µs
      message: 'network-check-target-ip-10-0-129-191: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-135-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "33454"
    uid: f389d08b-5156-423c-a241-bf7c13172790
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:06Z"
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.897242ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.048452ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 2.344339ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 2.296788ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 2.733063ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 2.641793ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 2.550567ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 2.857544ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:06Z"
    - latency: 2.352548ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:06Z"
    - latency: 2.186063ms
      message: 'network-check-target-ip-10-0-135-193: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-ip-10-0-143-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "33452"
    uid: ea407523-1a6f-4e1c-9843-d408f7574605
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:06Z"
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.935896ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.023122ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 2.387111ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 2.158015ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 2.383606ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 1.999415ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 2.088681ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 2.219878ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:06Z"
    - latency: 2.443206ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:06Z"
    - latency: 2.246209ms
      message: 'network-check-target-ip-10-0-143-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-191-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-191.us-east-2.compute.internal
      uid: a15803e1-fcd2-4dd5-a62f-fc0824558d0c
    resourceVersion: "32583"
    uid: cc391f07-bc4e-4a93-bb4d-19ddfef8c5c4
  spec:
    sourcePod: network-check-source-6f78d59f99-vscbh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.211µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 1.630063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 1.207832ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 1.684821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:24:06Z"
    - latency: 754.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 1.811317ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:23:06Z"
    - latency: 809.367µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 1.871409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:22:06Z"
    - latency: 902.113µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:21:06Z"
    - latency: 1.925525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:21:06Z"
kind: List
metadata:
  resourceVersion: ""