apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "23768"
    uid: dfb6e6d8-6fc4-44df-8d76-609cfccda5d5
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:07:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.073423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 797.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 958.723µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:19:00Z"
    - latency: 1.180173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:18:00Z"
    - latency: 1.014992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:17:00Z"
    - latency: 1.107764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:16:00Z"
    - latency: 779.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:15:00Z"
    - latency: 803.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:14:00Z"
    - latency: 824.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:13:00Z"
    - latency: 1.131944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "25195"
    uid: 094783f5-6ef1-4f32-a355-f7006b792f2a
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:06:00Z"
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.321578ms
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 6.3992ms
      message: 'load-balancer-api-external: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 6.642533ms
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 8.305431ms
      message: 'load-balancer-api-external: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 5.788336ms
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 8.440286ms
      message: 'load-balancer-api-external: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 3.893475ms
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 7.079667ms
      message: 'load-balancer-api-external: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 4.288746ms
      message: 'load-balancer-api-external: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 7.917733ms
      message: 'load-balancer-api-external: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:20:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "25196"
    uid: ca585282-214a-42fa-a040-e534f56ae7cc
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:06:00Z"
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.260173ms
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 6.466061ms
      message: 'load-balancer-api-internal: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 6.676505ms
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 8.411358ms
      message: 'load-balancer-api-internal: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 5.715228ms
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 8.517221ms
      message: 'load-balancer-api-internal: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 4.051558ms
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 7.124236ms
      message: 'load-balancer-api-internal: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 4.282939ms
      message: 'load-balancer-api-internal: tcp connection to ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 7.985172ms
      message: 'load-balancer-api-internal: resolved host name ae84b84dc22f74c26871f96f999a43b1-e971f7b9063f8480.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:20:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-network-check-target-ip-10-0-135-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "23767"
    uid: a809109c-4bd8-47f1-9e01-7881fc8ef234
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:07:00Z"
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.316585ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 2.259475ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 2.695124ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:19:00Z"
    - latency: 2.564751ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:18:00Z"
    - latency: 2.353814ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:17:00Z"
    - latency: 2.380301ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:16:00Z"
    - latency: 2.192863ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:15:00Z"
    - latency: 2.411559ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:14:00Z"
    - latency: 2.462119ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:13:00Z"
    - latency: 2.4249ms
      message: 'network-check-target-ip-10-0-135-134: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-network-check-target-ip-10-0-136-183
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "23765"
    uid: 7f452991-3727-4ba2-9780-4aedb274b805
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:07:00Z"
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.336µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 1.292903ms
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 903.533µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:19:00Z"
    - latency: 759.533µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:18:00Z"
    - latency: 785.647µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:17:00Z"
    - latency: 1.364682ms
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:16:00Z"
    - latency: 894.631µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:15:00Z"
    - latency: 1.029555ms
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:14:00Z"
    - latency: 1.420412ms
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:13:00Z"
    - latency: 900.794µs
      message: 'network-check-target-ip-10-0-136-183: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-network-check-target-ip-10-0-143-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "23766"
    uid: 4a30e7e7-5dd3-4fe2-8676-8d809e2b2a28
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:07:00Z"
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.999711ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 1.928986ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 1.99151ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:19:00Z"
    - latency: 1.93513ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:18:00Z"
    - latency: 1.838595ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:17:00Z"
    - latency: 2.035742ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:16:00Z"
    - latency: 1.963837ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:15:00Z"
    - latency: 2.031736ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:14:00Z"
    - latency: 1.824109ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:13:00Z"
    - latency: 1.934988ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T19:59:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-183-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-183.ec2.internal
      uid: 76bf7f00-f8b1-44ae-afc8-916029440c16
    resourceVersion: "25194"
    uid: 16e2189e-7570-47da-963f-e2ac782a67d6
  spec:
    sourcePod: network-check-source-685456655f-cf5xl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T20:06:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 886.856µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 1.743789ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:24:00Z"
    - latency: 912.549µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 1.926033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:23:00Z"
    - latency: 1.119167ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 1.856324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:22:00Z"
    - latency: 916.904µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 1.663707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:21:00Z"
    - latency: 913.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T20:20:00Z"
    - latency: 1.998132ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T20:20:00Z"
kind: List
metadata:
  resourceVersion: ""