apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "87919"
    uid: 0cc06150-b726-48b1-aea7-5bf6bf8812fb
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:49:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:48Z"
    - latency: 811.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 1.35325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 959.869µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 1.323583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 759.054µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 942.402µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:48Z"
    - latency: 1.078306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:48Z"
    - latency: 932.599µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:48Z"
    - latency: 1.103923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "85748"
    uid: 2d729d76-de06-491d-83a3-f35aef67eee0
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:48:48Z"
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.742194ms
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 7.465366ms
      message: 'load-balancer-api-external: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 4.003662ms
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 6.90342ms
      message: 'load-balancer-api-external: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 4.356735ms
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 6.581074ms
      message: 'load-balancer-api-external: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 4.543362ms
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 6.982559ms
      message: 'load-balancer-api-external: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 4.394193ms
      message: 'load-balancer-api-external: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 6.615204ms
      message: 'load-balancer-api-external: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:26:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "85747"
    uid: 55b70b6b-6064-428a-a26b-0e2978aceb24
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:48:48Z"
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.742059ms
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 7.514922ms
      message: 'load-balancer-api-internal: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 3.831044ms
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 6.861808ms
      message: 'load-balancer-api-internal: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 4.343415ms
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 6.687505ms
      message: 'load-balancer-api-internal: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 3.659793ms
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 6.903614ms
      message: 'load-balancer-api-internal: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 3.64632ms
      message: 'load-balancer-api-internal: tcp connection to a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 6.553026ms
      message: 'load-balancer-api-internal: resolved host name a40e87eaa52e5459eb5b0d0b4995d375-1bfac86081be61eb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:26:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-network-check-target-ip-10-0-140-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "87916"
    uid: 6746ccd3-0d16-4cf3-b7ac-7b2fec8bd42d
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:49:48Z"
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.497µs
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:48Z"
    - latency: 1.210343ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 903.177µs
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 938.574µs
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 1.199566ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 1.007269ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 809.874µs
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:48Z"
    - latency: 1.199486ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:48Z"
    - latency: 1.149388ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:48Z"
    - latency: 1.027847ms
      message: 'network-check-target-ip-10-0-140-36: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-network-check-target-ip-10-0-141-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "87918"
    uid: ab1ad7f3-8522-4ccf-ab53-99a6daac7482
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:49:48Z"
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346775ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:48Z"
    - latency: 2.124924ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 2.095533ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 2.672343ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 2.326947ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 1.909688ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 2.274577ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:48Z"
    - latency: 2.001896ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:48Z"
    - latency: 2.048678ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:48Z"
    - latency: 2.128551ms
      message: 'network-check-target-ip-10-0-141-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-network-check-target-ip-10-0-142-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "87917"
    uid: 8f232718-2e97-4955-a5df-4579ab2d189c
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:49:48Z"
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.964795ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:31:48Z"
    - latency: 2.290317ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 1.691055ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 2.289827ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 1.796457ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 2.202961ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 2.032415ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:25:48Z"
    - latency: 1.876866ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:24:48Z"
    - latency: 1.699287ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:23:48Z"
    - latency: 2.081016ms
      message: 'network-check-target-ip-10-0-142-140: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-36-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-36.ec2.internal
      uid: c7baf4ae-002a-48e1-9557-dc31252e5b08
    resourceVersion: "85746"
    uid: 0fa046df-563d-455d-add1-1b295c8cf772
  spec:
    sourcePod: network-check-source-7d88cb55d8-5tg5r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:48:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.986µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 1.837541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:30:48Z"
    - latency: 748.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 1.962814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:29:48Z"
    - latency: 1.157778ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 2.312866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:28:48Z"
    - latency: 868.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 1.706466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:27:48Z"
    - latency: 856.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:26:48Z"
    - latency: 1.634983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:26:48Z"
kind: List
metadata:
  resourceVersion: ""