apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "47625"
    uid: 45fac4ba-3357-42da-b0d6-d0e1c132103e
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:12:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068958ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 1.096946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 935.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 960.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:30:12Z"
    - latency: 1.108435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:29:12Z"
    - latency: 962.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:28:12Z"
    - latency: 899.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:27:12Z"
    - latency: 929.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:26:12Z"
    - latency: 920.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:25:12Z"
    - latency: 760.224µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:24:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "49766"
    uid: 366e2491-24c6-4e1e-ae65-8e37cefbc774
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:11:12Z"
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.174183ms
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 9.341292ms
      message: 'load-balancer-api-external: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 3.577429ms
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 7.602026ms
      message: 'load-balancer-api-external: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 2.918027ms
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 8.768612ms
      message: 'load-balancer-api-external: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 4.163679ms
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 7.701406ms
      message: 'load-balancer-api-external: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 5.028168ms
      message: 'load-balancer-api-external: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 8.309093ms
      message: 'load-balancer-api-external: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:31:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "49767"
    uid: 8bca79b2-3c3b-48e9-91b7-f06e3a206295
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:11:12Z"
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.242837ms
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 9.365345ms
      message: 'load-balancer-api-internal: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 3.950603ms
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 7.647293ms
      message: 'load-balancer-api-internal: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 2.992673ms
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 8.734755ms
      message: 'load-balancer-api-internal: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 4.186621ms
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 7.743507ms
      message: 'load-balancer-api-internal: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 4.702998ms
      message: 'load-balancer-api-internal: tcp connection to a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 8.191578ms
      message: 'load-balancer-api-internal: resolved host name a5ef1f814565348ec99b3cf98d89cb6d-b77ec33494048195.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:31:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-network-check-target-ip-10-0-133-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "47624"
    uid: 76f15719-ca17-4f23-845c-1423aa3d8702
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:12:12Z"
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.451563ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 2.299395ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 1.98893ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 1.901219ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:30:12Z"
    - latency: 2.180879ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:29:12Z"
    - latency: 2.250729ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:28:12Z"
    - latency: 1.981547ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:27:12Z"
    - latency: 2.052321ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:26:12Z"
    - latency: 2.286786ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:25:12Z"
    - latency: 2.356962ms
      message: 'network-check-target-ip-10-0-133-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:24:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-network-check-target-ip-10-0-141-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "47622"
    uid: 3bd981f4-6e17-4d57-8bb3-635218190702
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:12:12Z"
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03767ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 1.533904ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 1.003642ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 1.393242ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:30:12Z"
    - latency: 1.374531ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:29:12Z"
    - latency: 1.406443ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:28:12Z"
    - latency: 1.630071ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:27:12Z"
    - latency: 1.128043ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:26:12Z"
    - latency: 879.989µs
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:25:12Z"
    - latency: 1.108784ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:24:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-network-check-target-ip-10-0-143-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "47623"
    uid: 0c422559-896a-4bd9-9713-fcb3eeb16d7a
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:12:12Z"
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.555795ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 2.150939ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 2.696008ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 2.339914ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:30:12Z"
    - latency: 2.467423ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:29:12Z"
    - latency: 2.510401ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:28:12Z"
    - latency: 2.296257ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:27:12Z"
    - latency: 2.286855ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:26:12Z"
    - latency: 1.982574ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:25:12Z"
    - latency: 1.88211ms
      message: 'network-check-target-ip-10-0-143-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:24:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T07:05:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-37.ec2.internal
      uid: 02eb7578-c119-4027-ae5a-10530b3dcba3
    resourceVersion: "49765"
    uid: 1e184148-6a6d-4626-afe3-100644016223
  spec:
    sourcePod: network-check-source-869dcfcdcd-bh4jx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T07:11:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.718µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 1.838227ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:35:12Z"
    - latency: 1.247705ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 1.795766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:34:12Z"
    - latency: 1.066594ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 1.930805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:33:12Z"
    - latency: 990.897µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 1.536954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:32:12Z"
    - latency: 883.991µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T07:31:12Z"
    - latency: 1.943881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T07:31:12Z"
kind: List
metadata:
  resourceVersion: ""