apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61361"
    uid: 1bebae23-a3cb-4a20-b6a1-83b43bed1f46
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:36:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.257537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 820.638µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 972.184µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 1.01436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 965.557µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 1.060493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:06:40Z"
    - latency: 1.385503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:05:40Z"
    - latency: 1.134569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:04:40Z"
    - latency: 1.053067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:03:40Z"
    - latency: 936.176µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61363"
    uid: da09efc1-6ae8-47cc-89e0-9d594e003821
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:35:40Z"
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.637536ms
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 8.131089ms
      message: 'load-balancer-api-external: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 3.849444ms
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 8.835926ms
      message: 'load-balancer-api-external: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 4.268264ms
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 8.561626ms
      message: 'load-balancer-api-external: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 4.301955ms
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 7.439156ms
      message: 'load-balancer-api-external: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 4.257502ms
      message: 'load-balancer-api-external: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 7.336995ms
      message: 'load-balancer-api-external: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:07:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61362"
    uid: 28f6897b-efe2-4593-9475-6934fa279804
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:35:40Z"
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.669405ms
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 8.08638ms
      message: 'load-balancer-api-internal: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 4.455251ms
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 8.800413ms
      message: 'load-balancer-api-internal: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 4.325715ms
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 8.490779ms
      message: 'load-balancer-api-internal: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 3.843351ms
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 7.41651ms
      message: 'load-balancer-api-internal: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 4.809313ms
      message: 'load-balancer-api-internal: tcp connection to aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 7.319232ms
      message: 'load-balancer-api-internal: resolved host name aec396b6786554c2db4d5b6f203e796a-a049ac2b48f0a4cb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:07:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-129-15
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61358"
    uid: 5582030a-edc3-431c-9f19-c063478dfea0
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:36:40Z"
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321663ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 1.897933ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 2.410838ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 2.449418ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 2.270596ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 1.820775ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:06:40Z"
    - latency: 2.024626ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:05:40Z"
    - latency: 1.957003ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:04:40Z"
    - latency: 2.282027ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:03:40Z"
    - latency: 1.997088ms
      message: 'network-check-target-ip-10-0-129-15: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-132-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61360"
    uid: fb8654fe-b00a-4e5a-afcc-9ccd11f336c7
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:36:40Z"
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.27296ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 2.349357ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 2.564831ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 2.349828ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 2.284314ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 2.453343ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:06:40Z"
    - latency: 2.465059ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:05:40Z"
    - latency: 5.002322ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:04:40Z"
    - latency: 2.331163ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:03:40Z"
    - latency: 2.595479ms
      message: 'network-check-target-ip-10-0-132-2: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-ip-10-0-139-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61357"
    uid: f18f1347-2c56-4762-9cce-d1484d57905f
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:36:40Z"
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05607ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 962.342µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 1.221168ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 924.555µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 1.254223ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 1.357516ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:06:40Z"
    - latency: 1.021423ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:05:40Z"
    - latency: 3.99413ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:04:40Z"
    - latency: 1.14623ms
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:03:40Z"
    - latency: 874.22µs
      message: 'network-check-target-ip-10-0-139-42: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:02:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T09:29:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-42-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-42.ec2.internal
      uid: 2e1d7a4f-c1a1-4401-8dea-9ee3ec646155
    resourceVersion: "61359"
    uid: 2d1feb48-8b0c-40f4-bad0-d6bc18e3273c
  spec:
    sourcePod: network-check-source-869dcfcdcd-2jw44
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T09:35:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.251296ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 2.366926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:11:40Z"
    - latency: 903.021µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 1.704506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:10:40Z"
    - latency: 751.003µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 1.813259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:09:40Z"
    - latency: 874.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 1.794491ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:08:40Z"
    - latency: 1.296243ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:07:40Z"
    - latency: 1.717306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:07:40Z"
kind: List
metadata:
  resourceVersion: ""