apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "21817"
    uid: 219b2cc0-a10d-43d3-85cc-ee0fe6ff3a33
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:46:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.96µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T18:00:26Z"
    - latency: 1.028143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:59:26Z"
    - latency: 1.283548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:26Z"
    - latency: 1.338093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 1.039297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 994.638µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 892.542µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 989.026µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 972.776µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:26Z"
    - latency: 1.065692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "20424"
    uid: 97dcc984-fe49-4c8e-bd84-82ea4b2565c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:45:26Z"
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.202223ms
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 7.143553ms
      message: 'load-balancer-api-external: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 5.191733ms
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 6.327494ms
      message: 'load-balancer-api-external: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 5.981629ms
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 11.023004ms
      message: 'load-balancer-api-external: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 4.913148ms
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 6.544189ms
      message: 'load-balancer-api-external: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 5.04555ms
      message: 'load-balancer-api-external: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 7.572781ms
      message: 'load-balancer-api-external: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:53:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "20425"
    uid: 8f631b0e-9470-46b5-b737-2352d7d5396b
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:45:26Z"
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.202691ms
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 7.228373ms
      message: 'load-balancer-api-internal: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 5.221377ms
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 6.276784ms
      message: 'load-balancer-api-internal: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 5.97051ms
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 11.10402ms
      message: 'load-balancer-api-internal: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 4.86716ms
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 6.494727ms
      message: 'load-balancer-api-internal: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 5.060938ms
      message: 'load-balancer-api-internal: tcp connection to a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 7.55535ms
      message: 'load-balancer-api-internal: resolved host name a0bce42e2354945e5baa8b472e04e0ec-72dceb4d473f6f4e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:53:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-network-check-target-ip-10-0-133-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "21814"
    uid: 9978025f-e6a1-401a-8146-a251f35058ec
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:46:26Z"
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.509244ms
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T18:00:26Z"
    - latency: 937.779µs
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:59:26Z"
    - latency: 914.179µs
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:26Z"
    - latency: 1.467281ms
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 1.288261ms
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 938.926µs
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 1.185084ms
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 1.216039ms
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 922.95µs
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:26Z"
    - latency: 928.096µs
      message: 'network-check-target-ip-10-0-133-178: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-network-check-target-ip-10-0-139-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "21815"
    uid: 1816f973-c8c8-4c4e-a276-3dc047458354
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:46:26Z"
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.598348ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T18:00:26Z"
    - latency: 2.22954ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:59:26Z"
    - latency: 2.416831ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:26Z"
    - latency: 2.611564ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 2.411613ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 2.473034ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 2.284348ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 2.430343ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 2.707743ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:26Z"
    - latency: 2.674655ms
      message: 'network-check-target-ip-10-0-139-0: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-network-check-target-ip-10-0-143-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "21816"
    uid: 5b76e693-0bbd-41fb-ba72-8c64a0563b8f
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:46:26Z"
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.507809ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T18:00:26Z"
    - latency: 2.175275ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:59:26Z"
    - latency: 2.500233ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:26Z"
    - latency: 2.383692ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 2.283484ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 2.340433ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 2.617607ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 2.267453ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 2.307012ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:26Z"
    - latency: 2.399181ms
      message: 'network-check-target-ip-10-0-143-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:39:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-178.ec2.internal
      uid: d33ca805-c083-48dd-a4a2-4c344a00f16f
    resourceVersion: "20421"
    uid: 050dd6bf-cb93-4291-a4e1-4705ce83ae97
  spec:
    sourcePod: network-check-source-869dcfcdcd-4g8qt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:45:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 1.999134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:26Z"
    - latency: 1.001158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 1.663226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:26Z"
    - latency: 765.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 1.717221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:26Z"
    - latency: 818.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 1.540703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:26Z"
    - latency: 876.396µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:26Z"
    - latency: 2.277395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:53:26Z"
kind: List
metadata:
  resourceVersion: ""