apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "111545"
    uid: bddef3f3-d2db-4af7-b678-24681e620a9c
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:25Z"
    - latency: 1.021735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:25Z"
    - latency: 11.025254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:25Z"
    - latency: 977.921µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:25Z"
    - latency: 765.876µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 906.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 971.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 854.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 1.018979ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 1.328164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "108833"
    uid: ac2807aa-8769-4a41-a405-9b669ba743ff
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:25Z"
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 63.639131ms
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 7.332494ms
      message: 'load-balancer-api-external: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 51.767748ms
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 6.351437ms
      message: 'load-balancer-api-external: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 56.746782ms
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 6.818738ms
      message: 'load-balancer-api-external: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 51.556285ms
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 6.844868ms
      message: 'load-balancer-api-external: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 60.284589ms
      message: 'load-balancer-api-external: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 6.296614ms
      message: 'load-balancer-api-external: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "108832"
    uid: 5d4d81e2-1027-46f6-ae55-7e9165e1990b
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:25Z"
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.180583ms
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 7.263538ms
      message: 'load-balancer-api-internal: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 56.721547ms
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 6.411861ms
      message: 'load-balancer-api-internal: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 62.91447ms
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 6.910934ms
      message: 'load-balancer-api-internal: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 51.543563ms
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 6.894335ms
      message: 'load-balancer-api-internal: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 59.603026ms
      message: 'load-balancer-api-internal: tcp connection to a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 6.279126ms
      message: 'load-balancer-api-internal: resolved host name a8a1717a8546b4318bd8725a26f164b5-359068c9b1489aca.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-network-check-target-ip-10-0-128-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "111543"
    uid: c266f9cc-4025-468d-aaf8-e9382f8113a3
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:25Z"
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.057646ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:25Z"
    - latency: 2.047515ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:25Z"
    - latency: 10.533573ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:25Z"
    - latency: 2.054031ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:25Z"
    - latency: 1.693054ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 1.952235ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 2.023131ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 1.84256ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 1.93864ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 2.141999ms
      message: 'network-check-target-ip-10-0-128-245: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-network-check-target-ip-10-0-135-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "111542"
    uid: 315f8e54-a4a5-4d5f-8ffc-ef288a36690c
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:25Z"
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.162µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:25Z"
    - latency: 927.155µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:25Z"
    - latency: 9.993854ms
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:25Z"
    - latency: 966.452µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:25Z"
    - latency: 934.249µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 842.476µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 900.156µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 1.520884ms
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 921.973µs
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 1.256496ms
      message: 'network-check-target-ip-10-0-135-7: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-network-check-target-ip-10-0-136-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "111544"
    uid: 061a62c3-92c8-4127-9caa-59bcf4b136cd
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:01:25Z"
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.487242ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:04:25Z"
    - latency: 2.18989ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:25Z"
    - latency: 10.235399ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:25Z"
    - latency: 2.711114ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:25Z"
    - latency: 2.174871ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 2.410283ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 1.939836ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 2.770002ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 2.201524ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 2.281101ms
      message: 'network-check-target-ip-10-0-136-210: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:54:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-7.us-west-2.compute.internal
      uid: 5da30549-9d84-4720-a952-c2fc3b5cf817
    resourceVersion: "108831"
    uid: e3d0b9ea-205d-4d3c-8ea7-a79f0d7bf9e9
  spec:
    sourcePod: network-check-source-6f78d59f99-989z4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:00:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 744.376µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 2.540125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:25Z"
    - latency: 1.114264ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 1.787592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:25Z"
    - latency: 886.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 1.774775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:58:25Z"
    - latency: 952.164µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 1.851254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:25Z"
    - latency: 855.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:25Z"
    - latency: 1.685081ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:25Z"
kind: List
metadata:
  resourceVersion: ""