apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60073"
    uid: d25465e2-d829-40e5-8f88-85f55776e1f3
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:48:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.258259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 1.166676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 1.19267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 1.585363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 1.624269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 1.219298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:18:37Z"
    - latency: 1.213061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:17:37Z"
    - latency: 953.095µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:16:37Z"
    - latency: 984.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:37Z"
    - latency: 1.090696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60075"
    uid: a4146cf6-6fc9-4799-94a9-2c1ca4205543
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:47:37Z"
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.604723ms
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 7.055862ms
      message: 'load-balancer-api-external: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 5.139178ms
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 6.836288ms
      message: 'load-balancer-api-external: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 5.059561ms
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 7.757403ms
      message: 'load-balancer-api-external: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 8.0681ms
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 6.828776ms
      message: 'load-balancer-api-external: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 4.151844ms
      message: 'load-balancer-api-external: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 7.38758ms
      message: 'load-balancer-api-external: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60074"
    uid: 0b31008a-75ec-4c36-bae9-b481ce9b7a10
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:47:37Z"
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.948219ms
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 6.970092ms
      message: 'load-balancer-api-internal: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 5.170579ms
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 6.747763ms
      message: 'load-balancer-api-internal: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 5.209631ms
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 7.738496ms
      message: 'load-balancer-api-internal: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 7.616434ms
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 6.899984ms
      message: 'load-balancer-api-internal: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 4.782032ms
      message: 'load-balancer-api-internal: tcp connection to ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 7.358128ms
      message: 'load-balancer-api-internal: resolved host name ae7abe5125aa543d4b04780c7f6389d2-8ab79805027c641c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:19:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-network-check-target-ip-10-0-128-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60069"
    uid: 9add4c93-d847-46f3-a77c-6f400e9b77a7
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:48:37Z"
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.124141ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 2.754498ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 2.241223ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 2.711567ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 2.167437ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 2.481432ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:18:37Z"
    - latency: 2.456584ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:17:37Z"
    - latency: 2.432972ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:16:37Z"
    - latency: 2.438582ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:37Z"
    - latency: 2.297635ms
      message: 'network-check-target-ip-10-0-128-48: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-network-check-target-ip-10-0-135-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60070"
    uid: 811e1fcb-c571-44d9-894f-f3092cdcc1d3
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:48:37Z"
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.6185ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 1.501595ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 1.360375ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 888.62µs
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 869.919µs
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 893.519µs
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:18:37Z"
    - latency: 1.555503ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:17:37Z"
    - latency: 1.490686ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:16:37Z"
    - latency: 910.622µs
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:37Z"
    - latency: 1.255883ms
      message: 'network-check-target-ip-10-0-135-139: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-network-check-target-ip-10-0-141-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60072"
    uid: c6a1de1b-d956-4317-ba7a-1b283be43c6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:48:37Z"
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.005738ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 2.004982ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 1.874311ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 1.83726ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 1.991185ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 1.927321ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:18:37Z"
    - latency: 1.952715ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:17:37Z"
    - latency: 1.882624ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:16:37Z"
    - latency: 1.784089ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:37Z"
    - latency: 2.056363ms
      message: 'network-check-target-ip-10-0-141-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:41:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-139.ec2.internal
      uid: e3774640-b7ff-44cd-8e44-10886d85d7dc
    resourceVersion: "60071"
    uid: 3ce9f666-f2c2-440e-9baa-4723879ba5fa
  spec:
    sourcePod: network-check-source-869dcfcdcd-ffl9z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:47:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13232ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 1.923948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:23:37Z"
    - latency: 993.426µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 1.634839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:22:37Z"
    - latency: 827.399µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 2.048233ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:21:37Z"
    - latency: 900.665µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 2.08761ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:20:37Z"
    - latency: 909.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:19:37Z"
    - latency: 1.982367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:19:37Z"
kind: List
metadata:
  resourceVersion: ""