apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "47517"
    uid: f2776173-ee53-4442-bae1-f8063603c061
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:47:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.254571ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 1.064517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 1.296033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 1.187192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:05:27Z"
    - latency: 991.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:04:27Z"
    - latency: 902.801µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:03:27Z"
    - latency: 1.144387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:02:27Z"
    - latency: 858.59µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:01:27Z"
    - latency: 1.153436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:00:27Z"
    - latency: 1.052361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "50013"
    uid: 35d7199e-b573-480e-a4a2-237c647fe3d9
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:46:27Z"
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.540069ms
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 9.902297ms
      message: 'load-balancer-api-external: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 5.041287ms
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 9.504194ms
      message: 'load-balancer-api-external: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 5.31012ms
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 7.457644ms
      message: 'load-balancer-api-external: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 5.482953ms
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 8.498657ms
      message: 'load-balancer-api-external: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 5.329099ms
      message: 'load-balancer-api-external: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 8.537331ms
      message: 'load-balancer-api-external: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:06:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "50012"
    uid: 06f6e8b7-9ca1-4722-8663-ac1b61636320
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:46:27Z"
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.455763ms
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 9.829876ms
      message: 'load-balancer-api-internal: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 4.108787ms
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 9.588337ms
      message: 'load-balancer-api-internal: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 4.779782ms
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 7.517869ms
      message: 'load-balancer-api-internal: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 4.475137ms
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 8.373987ms
      message: 'load-balancer-api-internal: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 5.359415ms
      message: 'load-balancer-api-internal: tcp connection to aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 8.440076ms
      message: 'load-balancer-api-internal: resolved host name aa0b68143eff64f9b92426e6fd358318-b1c5999e402e7daf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:06:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-network-check-target-ip-10-0-130-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "47516"
    uid: 916f78f7-bb04-4f51-b40c-1d6288e10a60
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:47:27Z"
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.248969ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 2.367823ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 2.079781ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 2.406642ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:05:27Z"
    - latency: 2.080382ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:04:27Z"
    - latency: 2.198954ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:03:27Z"
    - latency: 2.340048ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:02:27Z"
    - latency: 2.036349ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:01:27Z"
    - latency: 1.728144ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:00:27Z"
    - latency: 1.973151ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-network-check-target-ip-10-0-131-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "47514"
    uid: 64d244f5-b5a2-41fb-a648-939a3130a8b5
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:47:27Z"
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.843µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 950.519µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 941.866µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 823.266µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:05:27Z"
    - latency: 882.816µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:04:27Z"
    - latency: 862.118µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:03:27Z"
    - latency: 1.192685ms
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:02:27Z"
    - latency: 834.383µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:01:27Z"
    - latency: 733.748µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:00:27Z"
    - latency: 908.247µs
      message: 'network-check-target-ip-10-0-131-181: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-network-check-target-ip-10-0-138-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "47515"
    uid: c0180f99-5f37-4e77-a35f-08e77c1e7faf
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:47:27Z"
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.840049ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 1.889888ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 2.303256ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 1.938189ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:05:27Z"
    - latency: 1.780842ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:04:27Z"
    - latency: 1.51446ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:03:27Z"
    - latency: 1.875769ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:02:27Z"
    - latency: 1.822343ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:01:27Z"
    - latency: 1.704842ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:00:27Z"
    - latency: 1.879656ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:59:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T01:40:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-181-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-181.ec2.internal
      uid: ef848b96-a538-4c39-9b48-a4d107fe8a44
    resourceVersion: "50011"
    uid: 8672e59b-9f05-4dcf-8987-bf14f65476d8
  spec:
    sourcePod: network-check-source-989f8b8dc-q6qdb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:46:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.724µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 1.77203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:10:27Z"
    - latency: 925.132µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 1.664747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:09:27Z"
    - latency: 819.663µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 1.996249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:08:27Z"
    - latency: 776.478µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 1.75431ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:07:27Z"
    - latency: 850.636µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T02:06:27Z"
    - latency: 1.713683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T02:06:27Z"
kind: List
metadata:
  resourceVersion: ""