apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "135094"
    uid: cb91fbff-a99e-45bd-b2ea-5240074c5f56
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:47:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 1.005961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:35Z"
    - latency: 1.350591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:35Z"
    - latency: 2.268104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:35Z"
    - latency: 971.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:35Z"
    - latency: 1.618203ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:31:35Z"
    - latency: 938.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:30:35Z"
    - latency: 927.607µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:29:35Z"
    - latency: 1.16211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:28:35Z"
    - latency: 2.698113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "140020"
    uid: 3aaaeee4-e185-4786-9b08-c66ee60b9609
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:46:35Z"
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.694268ms
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 7.509522ms
      message: 'load-balancer-api-external: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 21.837967ms
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 48.596354ms
      message: 'load-balancer-api-external: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 13.135456ms
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 7.427964ms
      message: 'load-balancer-api-external: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 18.092671ms
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 6.238946ms
      message: 'load-balancer-api-external: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 16.200519ms
      message: 'load-balancer-api-external: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 7.40523ms
      message: 'load-balancer-api-external: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:36:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "140021"
    uid: 18b2af4c-5d41-429d-82e7-beb9ae462dbf
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:46:35Z"
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.795429ms
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 7.434135ms
      message: 'load-balancer-api-internal: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 17.241943ms
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 54.944924ms
      message: 'load-balancer-api-internal: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 16.45336ms
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 7.354421ms
      message: 'load-balancer-api-internal: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 16.167094ms
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 6.296457ms
      message: 'load-balancer-api-internal: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 16.236295ms
      message: 'load-balancer-api-internal: tcp connection to a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 7.289666ms
      message: 'load-balancer-api-internal: resolved host name a6c5b6b5372f64fac9197addf127cfca-b918be34c32d7f9d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:36:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-network-check-target-ip-10-0-130-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "135088"
    uid: 4e8f701d-9ebb-4aa7-a9a5-fe1409ebbaf2
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:47:35Z"
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.462474ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 1.093807ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:35Z"
    - latency: 1.461513ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:35Z"
    - latency: 4.255759ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:35Z"
    - latency: 1.250863ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:35Z"
    - latency: 953.004µs
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:31:35Z"
    - latency: 955.402µs
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:30:35Z"
    - latency: 901.497µs
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:29:35Z"
    - latency: 1.020104ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:28:35Z"
    - latency: 3.437089ms
      message: 'network-check-target-ip-10-0-130-171: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-network-check-target-ip-10-0-130-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "135092"
    uid: ed8469be-02a2-443b-9c4c-9cf1e4b7f73c
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:47:35Z"
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.624182ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 2.334609ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:35Z"
    - latency: 2.354727ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:35Z"
    - latency: 2.73185ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:35Z"
    - latency: 2.305353ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:35Z"
    - latency: 2.169502ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:31:35Z"
    - latency: 2.25739ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:30:35Z"
    - latency: 2.644781ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:29:35Z"
    - latency: 2.36253ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:28:35Z"
    - latency: 3.943269ms
      message: 'network-check-target-ip-10-0-130-5: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-network-check-target-ip-10-0-131-254
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "135089"
    uid: 2bc229ac-336f-4d7b-bae1-03432f274cb3
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:47:35Z"
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.55429ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 2.288509ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:35:35Z"
    - latency: 2.513205ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:34:35Z"
    - latency: 3.766836ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:33:35Z"
    - latency: 2.435953ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:32:35Z"
    - latency: 2.292411ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:31:35Z"
    - latency: 2.003708ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:30:35Z"
    - latency: 2.264803ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:29:35Z"
    - latency: 2.272672ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:28:35Z"
    - latency: 11.708773ms
      message: 'network-check-target-ip-10-0-131-254: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:27:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T00:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-171.ec2.internal
      uid: 4341436a-9f7c-4f4c-9695-7968d9e0fba8
    resourceVersion: "140019"
    uid: 58c05b65-a097-429c-b7ee-df24cd0fdb17
  spec:
    sourcePod: network-check-source-6f78d59f99-gr6hz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T00:46:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083736ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 1.636244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:40:35Z"
    - latency: 3.363866ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 22.073537ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:39:35Z"
    - latency: 1.519923ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 1.934268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:38:35Z"
    - latency: 991.54µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 1.672793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:37:35Z"
    - latency: 1.529496ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T01:36:35Z"
    - latency: 2.279289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T01:36:35Z"
kind: List
metadata:
  resourceVersion: ""