apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62270"
    uid: 76eae3a4-5dd0-41ab-b626-302e316f463e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:05:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.783µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 913.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 1.286349ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 1.151068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 999.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 924.208µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:35:13Z"
    - latency: 1.042359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:34:13Z"
    - latency: 1.166528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:33:13Z"
    - latency: 912.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:32:13Z"
    - latency: 1.110539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:31:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62272"
    uid: 3dfc139f-45a4-452e-8698-e9e18aabea7d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:04:13Z"
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.23409ms
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 7.810672ms
      message: 'load-balancer-api-external: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 8.065363ms
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 6.397941ms
      message: 'load-balancer-api-external: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 5.157926ms
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 7.913343ms
      message: 'load-balancer-api-external: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 4.014272ms
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 7.133947ms
      message: 'load-balancer-api-external: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 6.189287ms
      message: 'load-balancer-api-external: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 7.166934ms
      message: 'load-balancer-api-external: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:36:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62271"
    uid: 39c14dc7-2ef4-450e-8354-c39270211b36
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:04:13Z"
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.240816ms
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 7.701321ms
      message: 'load-balancer-api-internal: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 3.919928ms
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 6.353255ms
      message: 'load-balancer-api-internal: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 5.228126ms
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 7.802685ms
      message: 'load-balancer-api-internal: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 3.997235ms
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 7.078228ms
      message: 'load-balancer-api-internal: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 6.210558ms
      message: 'load-balancer-api-internal: tcp connection to a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 6.945099ms
      message: 'load-balancer-api-internal: resolved host name a891cbfa5c3be41018df01fc2c184b7b-8d7ac3eb5be4ebdc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:36:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-133-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62266"
    uid: a18fd5b7-b877-46ae-95dd-e843ef71b997
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:05:13Z"
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.809205ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 2.526763ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 2.329637ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 2.275705ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 2.38737ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 1.994003ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:35:13Z"
    - latency: 2.512037ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:34:13Z"
    - latency: 2.857886ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:33:13Z"
    - latency: 2.089303ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:32:13Z"
    - latency: 2.129535ms
      message: 'network-check-target-ip-10-0-133-230: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:31:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-134-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62268"
    uid: 30e08633-bd92-4992-acb9-e553b8726909
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:05:13Z"
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.235707ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 2.768576ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 2.232272ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 2.559939ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 2.340061ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 2.552185ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:35:13Z"
    - latency: 2.480393ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:34:13Z"
    - latency: 2.784227ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:33:13Z"
    - latency: 2.160527ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:32:13Z"
    - latency: 1.764025ms
      message: 'network-check-target-ip-10-0-134-137: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:31:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-ip-10-0-138-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62267"
    uid: 377bc541-273f-420d-8399-1cbf63299cc4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:05:13Z"
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.231368ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 1.036383ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 1.38474ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 1.044242ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 1.345283ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 1.248809ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:35:13Z"
    - latency: 1.189336ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:34:13Z"
    - latency: 2.454191ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:33:13Z"
    - latency: 1.458889ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:32:13Z"
    - latency: 915.964µs
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:31:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T18:58:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-143.ec2.internal
      uid: 91e0537d-aacd-4ff7-b601-13abd4ef1473
    resourceVersion: "62269"
    uid: 7ebc46cf-430a-4595-b8f5-5b674e785cd9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-76rxf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T19:04:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.422457ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 1.696038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:40:13Z"
    - latency: 859.147µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 1.867978ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:39:13Z"
    - latency: 960.341µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 2.329749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:38:13Z"
    - latency: 939.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 1.870243ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:37:13Z"
    - latency: 773.379µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T19:36:13Z"
    - latency: 1.889679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T19:36:13Z"
kind: List
metadata:
  resourceVersion: ""