apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "78035"
    uid: 0a7d3be9-8a88-418c-9c91-235d37ad5da8
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:10:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:59:38Z"
    - latency: 913.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:58:38Z"
    - latency: 912.52µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 1.480209ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 1.24091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 1.240584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 1.0882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 927.583µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:52:38Z"
    - latency: 1.127085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:38Z"
    - latency: 1.045909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "75440"
    uid: 454e9c28-b0f6-4156-bcbf-7c43501171b4
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:09:38Z"
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.288068ms
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 6.676856ms
      message: 'load-balancer-api-external: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 3.999809ms
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 7.530635ms
      message: 'load-balancer-api-external: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 4.140821ms
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 7.436363ms
      message: 'load-balancer-api-external: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 4.822767ms
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 7.749999ms
      message: 'load-balancer-api-external: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 4.347384ms
      message: 'load-balancer-api-external: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 7.537075ms
      message: 'load-balancer-api-external: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:53:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "75441"
    uid: ff02d43f-7e16-4cd4-a38d-cb4d8e848358
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:09:38Z"
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.428521ms
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 6.619872ms
      message: 'load-balancer-api-internal: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 3.994547ms
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 7.555821ms
      message: 'load-balancer-api-internal: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 4.122159ms
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 7.618849ms
      message: 'load-balancer-api-internal: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 3.910049ms
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 7.796566ms
      message: 'load-balancer-api-internal: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 3.961259ms
      message: 'load-balancer-api-internal: tcp connection to ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 7.447661ms
      message: 'load-balancer-api-internal: resolved host name ab0a8b2cf91d64a39ac232a01ffcec25-ea14223f56942a49.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:53:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-133-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "78032"
    uid: 204a74b1-78e2-4e96-bc1c-c82d05ef42e4
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:10:38Z"
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.410124ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:59:38Z"
    - latency: 2.115652ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:58:38Z"
    - latency: 2.291918ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 2.446687ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 2.209166ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 2.277311ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 2.424455ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 2.29728ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:52:38Z"
    - latency: 2.590912ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:38Z"
    - latency: 2.066725ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-143-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "78034"
    uid: 061ee0a3-c93b-412c-8ab7-91e15dfcb9fb
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:10:38Z"
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.438796ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:59:38Z"
    - latency: 978.462µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:58:38Z"
    - latency: 1.006965ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 1.149112ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 1.25323ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 1.21754ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 923.069µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 935.355µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:52:38Z"
    - latency: 1.099577ms
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:38Z"
    - latency: 996.8µs
      message: 'network-check-target-ip-10-0-143-153: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-ip-10-0-143-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "78033"
    uid: e5aa4c92-68fa-4d05-98e5-cf1e35ecbebe
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:10:38Z"
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.249197ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:59:38Z"
    - latency: 2.278935ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:58:38Z"
    - latency: 2.356719ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 2.396125ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 2.377719ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 2.177923ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 2.264113ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 2.295259ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:52:38Z"
    - latency: 2.302505ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:51:38Z"
    - latency: 2.179091ms
      message: 'network-check-target-ip-10-0-143-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:50:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T13:03:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-153-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-153.ec2.internal
      uid: e53f73e8-0aa2-4c2a-b3e4-1087f89ffd51
    resourceVersion: "75439"
    uid: 9ab70962-b2c2-4ee5-ae10-d99bc36d0f55
  spec:
    sourcePod: network-check-source-7d88cb55d8-52sx8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T13:09:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 1.811041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:57:38Z"
    - latency: 1.00329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 1.853086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:56:38Z"
    - latency: 1.309762ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 2.075296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:55:38Z"
    - latency: 946.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 2.328487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:54:38Z"
    - latency: 862.36µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T13:53:38Z"
    - latency: 1.941673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T13:53:38Z"
kind: List
metadata:
  resourceVersion: ""