apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "169796"
    uid: 62fba331-c3f1-41df-9b84-2af60360fb65
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:59:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:44:44Z"
    - latency: 1.198002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:43:44Z"
    - latency: 1.286452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:42:44Z"
    - latency: 989.907µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:41:44Z"
    - latency: 1.21289ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 1.173014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 1.108703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 870.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 1.12689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 1.402222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:35:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "166477"
    uid: 8e455c96-a325-4acf-abbd-7b599746cc27
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:58:44Z"
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.697037ms
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 8.412857ms
      message: 'load-balancer-api-external: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 53.323817ms
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 14.436494ms
      message: 'load-balancer-api-external: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 51.396578ms
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 8.130102ms
      message: 'load-balancer-api-external: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 55.518898ms
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 9.657226ms
      message: 'load-balancer-api-external: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 51.197368ms
      message: 'load-balancer-api-external: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 8.715991ms
      message: 'load-balancer-api-external: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:36:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "166478"
    uid: 7b2e9ca3-1ee7-45c4-9fc2-0baffa7386a7
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:58:44Z"
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.71144ms
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 8.353844ms
      message: 'load-balancer-api-internal: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 56.178736ms
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 14.373389ms
      message: 'load-balancer-api-internal: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 55.495985ms
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 8.07538ms
      message: 'load-balancer-api-internal: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 51.846451ms
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 9.698497ms
      message: 'load-balancer-api-internal: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 56.789344ms
      message: 'load-balancer-api-internal: tcp connection to ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 8.640658ms
      message: 'load-balancer-api-internal: resolved host name ab176cf1b8f3e4b2b9a47658d610d089-75b99088ee9799d1.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:36:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-137-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "169792"
    uid: 24c95102-88e1-4543-b169-c3bdae10a78e
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:59:44Z"
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.141192ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:44:44Z"
    - latency: 2.233269ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:43:44Z"
    - latency: 2.985978ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:42:44Z"
    - latency: 2.584957ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:41:44Z"
    - latency: 2.5966ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 2.278498ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 2.954428ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 2.384893ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 2.971844ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 2.443689ms
      message: 'network-check-target-ip-10-0-137-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:35:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-139-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "169791"
    uid: e9c72951-475e-483e-8e75-840ee0069b14
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:59:44Z"
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.362297ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:44:44Z"
    - latency: 876.078µs
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:43:44Z"
    - latency: 1.061776ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:42:44Z"
    - latency: 1.364406ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:41:44Z"
    - latency: 1.61257ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 1.151669ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 1.075291ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 1.027533ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 1.553745ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 1.658067ms
      message: 'network-check-target-ip-10-0-139-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:35:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-ip-10-0-140-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "169793"
    uid: 6148a198-6d91-44bf-a1a5-146dc971a1db
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:59:44Z"
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.144338ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:44:44Z"
    - latency: 1.943695ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:43:44Z"
    - latency: 2.450241ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:42:44Z"
    - latency: 2.437764ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:41:44Z"
    - latency: 2.422467ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 2.226055ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 2.984893ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 2.368451ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 2.341096ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 2.444946ms
      message: 'network-check-target-ip-10-0-140-140: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:35:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T01:52:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-26.us-west-2.compute.internal
      uid: 87958765-84c3-4f97-b66d-622a8e1faf40
    resourceVersion: "166476"
    uid: df74dd59-eb30-4865-bcb4-5f9518626a2f
  spec:
    sourcePod: network-check-source-6f78d59f99-z28hp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:58:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 936.041µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:40:44Z"
    - latency: 1.024506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 649.567µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:39:44Z"
    - latency: 4.158377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 11.871015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:38:44Z"
    - latency: 1.044976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 841.254µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:37:44Z"
    - latency: 1.07336ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T03:36:44Z"
    - latency: 670.745µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T03:36:44Z"
kind: List
metadata:
  resourceVersion: ""