apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "23055"
    uid: ef19193b-836f-46c7-af3c-bf3d3300392a
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 871.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:12:17Z"
    - latency: 901.222µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:11:17Z"
    - latency: 976.392µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:10:17Z"
    - latency: 1.03635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 970.603µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 1.010959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 858.526µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 996.679µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 1.140365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:04:17Z"
    - latency: 854.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "21533"
    uid: defd7c89-0267-44c1-8c04-1d76455c33d5
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:17Z"
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.906367ms
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 8.570788ms
      message: 'load-balancer-api-external: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 5.7452ms
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 7.781026ms
      message: 'load-balancer-api-external: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 5.775592ms
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 8.063169ms
      message: 'load-balancer-api-external: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 6.012426ms
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 8.796707ms
      message: 'load-balancer-api-external: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 3.999508ms
      message: 'load-balancer-api-external: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 8.54689ms
      message: 'load-balancer-api-external: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:05:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "21532"
    uid: 08d59fa6-5b89-492f-848d-b20adc539bcf
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:17Z"
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.944854ms
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 8.516777ms
      message: 'load-balancer-api-internal: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 5.250724ms
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 7.805656ms
      message: 'load-balancer-api-internal: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 5.743266ms
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 7.88856ms
      message: 'load-balancer-api-internal: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 6.051323ms
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 8.841205ms
      message: 'load-balancer-api-internal: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 3.958263ms
      message: 'load-balancer-api-internal: tcp connection to aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 8.702556ms
      message: 'load-balancer-api-internal: resolved host name aaac05de345174778a5bfbac0e005b56-aa042e456ed8bba0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:05:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-131-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "23054"
    uid: b08ba6c3-4433-463c-a54f-374634c32226
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:17Z"
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043298ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:12:17Z"
    - latency: 2.209046ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:11:17Z"
    - latency: 2.295909ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:10:17Z"
    - latency: 2.278485ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 2.015228ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 2.32873ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 1.908893ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 2.225447ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 2.11096ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:04:17Z"
    - latency: 2.229322ms
      message: 'network-check-target-ip-10-0-131-158: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-133-218
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "23052"
    uid: c217cc53-6c57-4832-9721-cdbe995d887a
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:17Z"
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.286µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:12:17Z"
    - latency: 995.208µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:11:17Z"
    - latency: 862.893µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:10:17Z"
    - latency: 1.434924ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 770.178µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 1.00641ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 864.228µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 825.797µs
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 1.079251ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:04:17Z"
    - latency: 1.008267ms
      message: 'network-check-target-ip-10-0-133-218: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-ip-10-0-143-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "23053"
    uid: 6864feac-c601-451c-ba03-d6f6271607ba
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:58:17Z"
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.207424ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:12:17Z"
    - latency: 2.164807ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:11:17Z"
    - latency: 2.384097ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:10:17Z"
    - latency: 2.406434ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 2.272297ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 2.311177ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 2.3306ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 1.865014ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 2.141469ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:04:17Z"
    - latency: 2.22756ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:03:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T12:51:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-218-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-218.ec2.internal
      uid: 30b03f22-54cd-4d58-9a25-78f9fbb9f185
    resourceVersion: "21531"
    uid: 833eb0b5-dc52-4aa1-9992-f7f1bf7e5a2f
  spec:
    sourcePod: network-check-source-6f8b768455-jl4wt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T12:57:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 2.078725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:09:17Z"
    - latency: 800.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 1.628842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:08:17Z"
    - latency: 1.099184ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 1.907064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:07:17Z"
    - latency: 821.45µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 1.6392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:06:17Z"
    - latency: 919.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T13:05:17Z"
    - latency: 2.208757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T13:05:17Z"
kind: List
metadata:
  resourceVersion: ""