apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "132347"
    uid: c0002951-3598-4aab-987d-404e12036feb
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:46:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.327073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 964.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 1.624044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 1.203009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 1.696379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:03Z"
    - latency: 1.151244ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:03Z"
    - latency: 1.592551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:03Z"
    - latency: 1.32052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:03Z"
    - latency: 1.445383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:03Z"
    - latency: 1.206529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "133562"
    uid: 557826de-7573-47d3-9cdc-040a1118ba2b
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:45:03Z"
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.909023ms
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 6.979776ms
      message: 'load-balancer-api-external: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 63.626711ms
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 7.614104ms
      message: 'load-balancer-api-external: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 61.871617ms
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 7.165158ms
      message: 'load-balancer-api-external: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 56.65387ms
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 7.947329ms
      message: 'load-balancer-api-external: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 62.867745ms
      message: 'load-balancer-api-external: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 6.840767ms
      message: 'load-balancer-api-external: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "133561"
    uid: 1aec5808-9f4e-46ed-adbc-b6c65896a747
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:45:03Z"
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.924065ms
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 6.908135ms
      message: 'load-balancer-api-internal: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 55.740694ms
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 7.586179ms
      message: 'load-balancer-api-internal: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 58.077068ms
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 7.102775ms
      message: 'load-balancer-api-internal: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 56.59427ms
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 7.907995ms
      message: 'load-balancer-api-internal: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 60.147535ms
      message: 'load-balancer-api-internal: tcp connection to ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 6.768368ms
      message: 'load-balancer-api-internal: resolved host name ac60eab6f532d4004a67394301a17821-2cf05b1ccc71f3c2.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-133-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "132344"
    uid: c023163a-d3b9-4bd4-ab04-4f7dfa82f9ff
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:46:03Z"
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.478519ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 2.519978ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 2.213999ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 2.467629ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 4.323183ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:03Z"
    - latency: 2.355815ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:03Z"
    - latency: 2.721617ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:03Z"
    - latency: 2.639365ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:03Z"
    - latency: 3.341691ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:03Z"
    - latency: 2.751874ms
      message: 'network-check-target-ip-10-0-133-5: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-139-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "132343"
    uid: 78e6f828-edba-4358-ae26-4feed55ebd28
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:46:03Z"
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.383303ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 1.053067ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 981.925µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 1.319359ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 2.022303ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:03Z"
    - latency: 1.913969ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:03Z"
    - latency: 929.359µs
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:03Z"
    - latency: 1.527013ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:03Z"
    - latency: 1.751215ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:03Z"
    - latency: 2.535272ms
      message: 'network-check-target-ip-10-0-139-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "132342"
    uid: 0fd41bbe-f304-4b1e-81c3-028341edefaa
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:46:03Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376441ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 2.640255ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 2.256344ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 2.441145ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 2.715431ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:03Z"
    - latency: 2.34861ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:03Z"
    - latency: 2.790784ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:03Z"
    - latency: 2.748602ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:03Z"
    - latency: 2.832941ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:48:03Z"
    - latency: 2.711081ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:47:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:39:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-46.us-west-2.compute.internal
      uid: 7fd386c3-cc2f-49c9-b9d3-7b9e0be72a99
    resourceVersion: "133560"
    uid: 85260614-c96a-4a13-a651-0e739345996d
  spec:
    sourcePod: network-check-source-6f78d59f99-58v4l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:45:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 788.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 1.806333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:03Z"
    - latency: 1.165697ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 2.244684ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:03Z"
    - latency: 898.823µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 1.820121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:03Z"
    - latency: 1.16021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 2.108844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:03Z"
    - latency: 872.97µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:03Z"
    - latency: 1.708844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:03Z"
kind: List
metadata:
  resourceVersion: ""