apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "47537"
    uid: 815b9b90-7d95-4011-a188-87672f22dbbe
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:10:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.357µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 1.067978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 1.11293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 935.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:28:10Z"
    - latency: 1.096421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:27:10Z"
    - latency: 1.409446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:26:10Z"
    - latency: 1.134066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:25:10Z"
    - latency: 1.155556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:24:10Z"
    - latency: 1.042279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:23:10Z"
    - latency: 865.788µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "50102"
    uid: f2a53810-cbb8-4472-8c63-624edb922c79
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:09:10Z"
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.087534ms
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 7.007798ms
      message: 'load-balancer-api-external: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 5.702492ms
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 6.707251ms
      message: 'load-balancer-api-external: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 6.180969ms
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 8.69679ms
      message: 'load-balancer-api-external: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 3.934929ms
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 6.552645ms
      message: 'load-balancer-api-external: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 2.868942ms
      message: 'load-balancer-api-external: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 6.860533ms
      message: 'load-balancer-api-external: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:29:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "50103"
    uid: c570d951-4fe3-4596-abd2-0b6702eb3f49
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:09:10Z"
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.560609ms
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 7.038177ms
      message: 'load-balancer-api-internal: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 5.600171ms
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 6.686359ms
      message: 'load-balancer-api-internal: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 6.168933ms
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 8.758563ms
      message: 'load-balancer-api-internal: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 3.925296ms
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 6.574954ms
      message: 'load-balancer-api-internal: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 2.839882ms
      message: 'load-balancer-api-internal: tcp connection to a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 6.736158ms
      message: 'load-balancer-api-internal: resolved host name a20b43014967245888f2484ff6366ef6-4ddbcd4b72c76f41.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:29:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-132-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "47536"
    uid: a4d1250b-f998-42ad-a9cb-e085b07ee65d
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:10:10Z"
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.299486ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 2.254993ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 2.264399ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 2.237119ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:28:10Z"
    - latency: 2.262339ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:27:10Z"
    - latency: 2.498369ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:26:10Z"
    - latency: 2.261609ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:25:10Z"
    - latency: 2.385804ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:24:10Z"
    - latency: 2.441504ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:23:10Z"
    - latency: 2.204752ms
      message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-137-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "47534"
    uid: 61eb7ae1-e2bf-4bc0-b9f1-939387c2dc5a
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:10:10Z"
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.085µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 864.727µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 817.689µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 909.224µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:28:10Z"
    - latency: 1.36287ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:27:10Z"
    - latency: 879.38µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:26:10Z"
    - latency: 799.432µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:25:10Z"
    - latency: 1.317075ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:24:10Z"
    - latency: 1.056101ms
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:23:10Z"
    - latency: 827.661µs
      message: 'network-check-target-ip-10-0-137-40: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-ip-10-0-141-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "47535"
    uid: 805311ac-24dc-4747-aef5-9e3975673a3c
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:10:10Z"
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.359155ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 2.399968ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 2.638283ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 2.273938ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:28:10Z"
    - latency: 2.098987ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:27:10Z"
    - latency: 2.728207ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:26:10Z"
    - latency: 2.211625ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:25:10Z"
    - latency: 2.422995ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:24:10Z"
    - latency: 2.470825ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:23:10Z"
    - latency: 2.269322ms
      message: 'network-check-target-ip-10-0-141-199: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:22:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T04:03:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-40.ec2.internal
      uid: 98904d23-dc03-4daa-bcf1-f524be70ac49
    resourceVersion: "50101"
    uid: 71dd15e1-6f12-4243-8aaf-cd89a0ece00e
  spec:
    sourcePod: network-check-source-989f8b8dc-vmhmm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T04:09:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.903µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 1.838289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:33:10Z"
    - latency: 947.054µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 2.263073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:32:10Z"
    - latency: 1.062684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 1.868125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:31:10Z"
    - latency: 907.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 1.599715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:30:10Z"
    - latency: 1.208992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T04:29:10Z"
    - latency: 1.642757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T04:29:10Z"
kind: List
metadata:
  resourceVersion: ""