apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "52724"
    uid: b5333f04-d0aa-404e-8ea7-b142eaad4c44
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 1.087737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 1.073348ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 1.112696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:01Z"
    - latency: 893.277µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:01Z"
    - latency: 1.049494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:01Z"
    - latency: 1.108484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:01Z"
    - latency: 1.21327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:01Z"
    - latency: 1.090677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:01Z"
    - latency: 990.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "54845"
    uid: 3e512de7-6a08-465d-b43a-c7b7d379357c
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:01Z"
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907932ms
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 7.498768ms
      message: 'load-balancer-api-external: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 4.2267ms
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 8.23625ms
      message: 'load-balancer-api-external: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 3.649309ms
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 6.638423ms
      message: 'load-balancer-api-external: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 4.898898ms
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 9.013296ms
      message: 'load-balancer-api-external: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 4.81865ms
      message: 'load-balancer-api-external: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 6.275109ms
      message: 'load-balancer-api-external: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "54844"
    uid: 2832b4a9-0eef-4b41-ace7-b0c16e65199e
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:01Z"
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.102607ms
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 7.533451ms
      message: 'load-balancer-api-internal: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 4.294502ms
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 8.281642ms
      message: 'load-balancer-api-internal: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 4.19645ms
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 6.752188ms
      message: 'load-balancer-api-internal: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 4.3746ms
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 9.094968ms
      message: 'load-balancer-api-internal: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 4.779979ms
      message: 'load-balancer-api-internal: tcp connection to a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 6.305346ms
      message: 'load-balancer-api-internal: resolved host name a806cd132d9384d29abf09ccad5aeb49-82f126a7a33e3701.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-134-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "52721"
    uid: 10a4802a-4af4-4766-af34-f73ccb4e5639
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:01Z"
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.453209ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 1.424006ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 908.568µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 1.102393ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:01Z"
    - latency: 1.407127ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:01Z"
    - latency: 1.353365ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:01Z"
    - latency: 977.226µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:01Z"
    - latency: 848.477µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:01Z"
    - latency: 1.1556ms
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:01Z"
    - latency: 857.863µs
      message: 'network-check-target-ip-10-0-134-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-134-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "52722"
    uid: dfc117fb-b596-411d-9d36-91c49c97386d
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:01Z"
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.912759ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 2.053687ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 1.996271ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 2.024282ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:01Z"
    - latency: 2.116142ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:01Z"
    - latency: 1.969645ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:01Z"
    - latency: 2.05479ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:01Z"
    - latency: 5.538683ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:01Z"
    - latency: 2.124971ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:01Z"
    - latency: 1.529932ms
      message: 'network-check-target-ip-10-0-134-6: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-ip-10-0-139-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "52723"
    uid: c3f8fe89-389b-4013-963f-28382721f536
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:08:01Z"
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.337467ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 2.163864ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 2.360433ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 2.381557ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:01Z"
    - latency: 2.108697ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:01Z"
    - latency: 2.341666ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:01Z"
    - latency: 2.308885ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:01Z"
    - latency: 5.164523ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:01Z"
    - latency: 2.44454ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:01Z"
    - latency: 2.012777ms
      message: 'network-check-target-ip-10-0-139-165: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-100.ec2.internal
      uid: 35670ff1-5749-49d3-b30d-84585a8583c4
    resourceVersion: "54843"
    uid: 344b0d10-87bc-451c-a5c2-d98255fb1cc4
  spec:
    sourcePod: network-check-source-6f8b768455-x5fnd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.188314ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 2.302704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:31:01Z"
    - latency: 718.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 1.947101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:01Z"
    - latency: 917.114µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 1.825891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:01Z"
    - latency: 762.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 2.011871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:01Z"
    - latency: 944.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:01Z"
    - latency: 1.791343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:01Z"
kind: List
metadata:
  resourceVersion: ""