apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "39106"
    uid: 5be8206c-d120-46f1-88c0-292cdbe851f7
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:14:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276114ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 1.080587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 1.156012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:26:14Z"
    - latency: 1.232878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:25:14Z"
    - latency: 1.20939ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:24:14Z"
    - latency: 855.639µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:23:14Z"
    - latency: 1.189284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:22:14Z"
    - latency: 891.615µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:21:14Z"
    - latency: 1.016584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:20:14Z"
    - latency: 992.053µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:19:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "42259"
    uid: 3b17d8d7-00c5-4034-92ce-7b3e4e197472
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:13:14Z"
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.596541ms
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 6.267058ms
      message: 'load-balancer-api-external: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 3.447153ms
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 6.584735ms
      message: 'load-balancer-api-external: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 4.416937ms
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 6.301016ms
      message: 'load-balancer-api-external: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 3.88924ms
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 7.429898ms
      message: 'load-balancer-api-external: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 4.101854ms
      message: 'load-balancer-api-external: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 7.772442ms
      message: 'load-balancer-api-external: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "42260"
    uid: 100c0726-62bd-45cf-9c2b-6129bc1017d5
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:13:14Z"
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.618559ms
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 6.189549ms
      message: 'load-balancer-api-internal: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 4.924188ms
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 6.53306ms
      message: 'load-balancer-api-internal: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 3.739596ms
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 6.332138ms
      message: 'load-balancer-api-internal: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 3.373372ms
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 7.494452ms
      message: 'load-balancer-api-internal: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 4.199711ms
      message: 'load-balancer-api-internal: tcp connection to aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 7.605197ms
      message: 'load-balancer-api-internal: resolved host name aba92577f73224a69806b4f0a9f97401-753e92cff437b2e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-network-check-target-ip-10-0-131-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "39104"
    uid: 28d17b13-9730-49aa-ab34-ca97e6a58144
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:14:14Z"
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261471ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 1.983815ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 1.742209ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:26:14Z"
    - latency: 1.975226ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:25:14Z"
    - latency: 1.8014ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:24:14Z"
    - latency: 1.758085ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:23:14Z"
    - latency: 1.999544ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:22:14Z"
    - latency: 2.163524ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:21:14Z"
    - latency: 2.278059ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:20:14Z"
    - latency: 1.969512ms
      message: 'network-check-target-ip-10-0-131-207: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:19:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-network-check-target-ip-10-0-132-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "39105"
    uid: 50fd08cf-f4a1-4f06-b579-81ad5a4a6405
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:14:14Z"
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.354654ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 2.268845ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 2.32799ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:26:14Z"
    - latency: 2.148095ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:25:14Z"
    - latency: 2.018093ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:24:14Z"
    - latency: 2.280106ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:23:14Z"
    - latency: 2.104167ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:22:14Z"
    - latency: 2.350801ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:21:14Z"
    - latency: 2.251475ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:20:14Z"
    - latency: 2.153308ms
      message: 'network-check-target-ip-10-0-132-255: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:19:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-network-check-target-ip-10-0-139-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "39103"
    uid: 00e0df8d-12b6-4758-80f1-f63147546a0b
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:14:14Z"
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938µs
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 859.424µs
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 904.08µs
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:26:14Z"
    - latency: 1.078436ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:25:14Z"
    - latency: 1.013883ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:24:14Z"
    - latency: 964.151µs
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:23:14Z"
    - latency: 1.50839ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:22:14Z"
    - latency: 1.236879ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:21:14Z"
    - latency: 1.148424ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:20:14Z"
    - latency: 1.152124ms
      message: 'network-check-target-ip-10-0-139-200: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:19:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T01:07:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-200.ec2.internal
      uid: 68bab27b-6b12-478c-8cc4-0ed95ee0ebf6
    resourceVersion: "42258"
    uid: a391a6ac-6b6e-4b6d-95a4-77d2dca0f09f
  spec:
    sourcePod: network-check-source-dbd9cf844-45r2t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T01:13:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.86µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 1.799359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:31:14Z"
    - latency: 911.859µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 1.778131ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:30:14Z"
    - latency: 1.081094ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 1.668499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:29:14Z"
    - latency: 1.365542ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 1.972359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:28:14Z"
    - latency: 1.175329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T01:27:14Z"
    - latency: 1.785083ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T01:27:14Z"
kind: List
metadata:
  resourceVersion: ""