apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "22464"
    uid: 71ef6766-b499-4ce8-9def-21de230ded63
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:11:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.310643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:32:15Z"
    - latency: 822.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:31:15Z"
    - latency: 864.024µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:30:15Z"
    - latency: 962.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:29:15Z"
    - latency: 973.973µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 1.298027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 931.669µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 888.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 854.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 1.656746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "20616"
    uid: 8e36db86-ff87-44c5-ae83-123b674a7df3
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:10:15Z"
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.991659ms
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 8.564728ms
      message: 'load-balancer-api-external: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 4.301336ms
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 8.88203ms
      message: 'load-balancer-api-external: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 6.352768ms
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 8.752002ms
      message: 'load-balancer-api-external: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 5.718698ms
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 8.585634ms
      message: 'load-balancer-api-external: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 4.212677ms
      message: 'load-balancer-api-external: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 8.702819ms
      message: 'load-balancer-api-external: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:24:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "20615"
    uid: c365b38e-19f8-4011-a6ec-5625157c01c6
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:10:15Z"
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.073788ms
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 8.734647ms
      message: 'load-balancer-api-internal: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 5.38421ms
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 9.003848ms
      message: 'load-balancer-api-internal: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 6.394447ms
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 8.688624ms
      message: 'load-balancer-api-internal: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 5.667195ms
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 8.797138ms
      message: 'load-balancer-api-internal: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 4.224547ms
      message: 'load-balancer-api-internal: tcp connection to ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 8.834705ms
      message: 'load-balancer-api-internal: resolved host name ab548134fbb5b4037bb66566eee7b06c-ae3eea507bbf22d9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:24:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-131-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "22462"
    uid: d71d7d1b-77d7-433a-8f90-90ad53a791a3
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:11:15Z"
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.089µs
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:32:15Z"
    - latency: 871.19µs
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:31:15Z"
    - latency: 1.810896ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:30:15Z"
    - latency: 1.832714ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:29:15Z"
    - latency: 1.282074ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 1.469405ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 903.727µs
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 1.317058ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 858.504µs
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 2.221458ms
      message: 'network-check-target-ip-10-0-131-93: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-136-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "22463"
    uid: 06166be7-a290-4983-813d-109f715c7a0f
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:11:15Z"
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.449607ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:32:15Z"
    - latency: 1.916567ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:31:15Z"
    - latency: 2.570279ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:30:15Z"
    - latency: 2.463093ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:29:15Z"
    - latency: 2.237045ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 1.812828ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 2.148931ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 2.243222ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 2.181197ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 2.172427ms
      message: 'network-check-target-ip-10-0-136-245: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-network-check-target-ip-10-0-142-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "22465"
    uid: 2ac6bbbe-b448-4679-9013-59d09b94aba0
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:11:15Z"
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.415382ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:32:15Z"
    - latency: 2.246483ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:31:15Z"
    - latency: 2.303115ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:30:15Z"
    - latency: 2.63742ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:29:15Z"
    - latency: 2.190262ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 2.049877ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 2.487633ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 2.346166ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 2.190793ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 2.560677ms
      message: 'network-check-target-ip-10-0-142-13: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:23:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T08:04:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-93-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-93.ec2.internal
      uid: 523454cf-c19a-48c5-ab8b-f86e4d71faae
    resourceVersion: "20614"
    uid: ce5d9e23-e521-4363-8991-cdc4b97ddee0
  spec:
    sourcePod: network-check-source-6f8b768455-bwzr5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T08:10:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 1.96749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:28:15Z"
    - latency: 804.47µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 2.098407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:27:15Z"
    - latency: 1.073603ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 1.948024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:26:15Z"
    - latency: 1.418032ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 1.764811ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:25:15Z"
    - latency: 1.207863ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T08:24:15Z"
    - latency: 2.294286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T08:24:15Z"
kind: List
metadata:
  resourceVersion: ""