apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "27726"
    uid: 92d699c2-df39-4865-bae7-7d3c0639ec2f
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:25:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:32:43Z"
    - latency: 994.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:43Z"
    - latency: 1.039706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 899.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 1.009768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 1.079732ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 1.024659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 1.024932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:43Z"
    - latency: 1.001944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:43Z"
    - latency: 1.111824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "26531"
    uid: 560d97ce-913c-4336-8fe0-e95f01be6130
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:24:44Z"
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.877333ms
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 7.109205ms
      message: 'load-balancer-api-external: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 5.764717ms
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 7.635327ms
      message: 'load-balancer-api-external: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 3.575482ms
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 7.507915ms
      message: 'load-balancer-api-external: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 3.22602ms
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 7.060226ms
      message: 'load-balancer-api-external: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 5.227949ms
      message: 'load-balancer-api-external: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 7.939394ms
      message: 'load-balancer-api-external: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:26:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "26532"
    uid: f49599ef-570f-44ae-a696-724aab73d121
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:24:44Z"
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.905576ms
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 6.909166ms
      message: 'load-balancer-api-internal: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 5.75602ms
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 7.621073ms
      message: 'load-balancer-api-internal: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 3.80887ms
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 7.440347ms
      message: 'load-balancer-api-internal: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 4.604732ms
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 7.029918ms
      message: 'load-balancer-api-internal: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 5.24956ms
      message: 'load-balancer-api-internal: tcp connection to aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 7.856012ms
      message: 'load-balancer-api-internal: resolved host name aa5aa095dae5643fa98b853eda8d3ef9-ce0b6ab1ff708212.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:26:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-network-check-target-ip-10-0-133-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "27722"
    uid: ef042009-b4c4-4d11-89a3-fcc4e654fcd5
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:25:43Z"
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.295887ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:32:43Z"
    - latency: 1.636068ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:43Z"
    - latency: 919.093µs
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 794.044µs
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 1.591332ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 1.20093ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 994.561µs
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 1.417072ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:43Z"
    - latency: 1.687018ms
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:43Z"
    - latency: 847.377µs
      message: 'network-check-target-ip-10-0-133-199: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-network-check-target-ip-10-0-140-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "27725"
    uid: 6e0afa6b-aa6c-4b56-9067-ecd380eca81f
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:25:43Z"
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.106301ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:32:43Z"
    - latency: 1.963024ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:43Z"
    - latency: 2.006986ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 1.862449ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 2.200139ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 1.974813ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 2.142748ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 2.327326ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:43Z"
    - latency: 2.163586ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:43Z"
    - latency: 1.810252ms
      message: 'network-check-target-ip-10-0-140-112: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "27724"
    uid: e8389eb0-3067-4798-b002-46f6d88d0454
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:25:43Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249468ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:32:43Z"
    - latency: 2.591309ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:31:43Z"
    - latency: 1.913382ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 2.372477ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 2.253509ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 2.34431ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 1.817123ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 2.320842ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:25:43Z"
    - latency: 2.34062ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:24:43Z"
    - latency: 2.251676ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:23:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T21:18:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-199.ec2.internal
      uid: 4cb52d90-7d61-4614-8405-dca901fa7a88
    resourceVersion: "26530"
    uid: 552c97e6-3dd3-497c-a86d-30650ba0d15d
  spec:
    sourcePod: network-check-source-56499946bc-ssmgv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T21:24:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 2.051325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:30:43Z"
    - latency: 830.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 2.463171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:29:43Z"
    - latency: 1.127635ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 2.38331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:28:43Z"
    - latency: 937.385µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 2.021925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:27:43Z"
    - latency: 895.75µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T21:26:43Z"
    - latency: 1.826593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T21:26:43Z"
kind: List
metadata:
  resourceVersion: ""