apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32629"
    uid: 8b3a658b-5ef5-447e-b0b4-40d38c7c96fb
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 876.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 1.076849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 901.237µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 910.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 1.032308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 1.778508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:29:10Z"
    - latency: 1.126576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:28:10Z"
    - latency: 1.187318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:27:10Z"
    - latency: 1.003744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:26:10Z"
    - latency: 1.012317ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32631"
    uid: eafc5a0b-1a96-4efe-a59e-6c07fb65637d
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:10Z"
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.162354ms
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 8.428226ms
      message: 'load-balancer-api-external: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 3.663912ms
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 11.245431ms
      message: 'load-balancer-api-external: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 5.133778ms
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 8.505892ms
      message: 'load-balancer-api-external: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 5.047093ms
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 8.914598ms
      message: 'load-balancer-api-external: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 4.484845ms
      message: 'load-balancer-api-external: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 8.979664ms
      message: 'load-balancer-api-external: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32630"
    uid: 087b28c1-452c-45ef-b319-e44051acd0c0
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:10Z"
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.15372ms
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 8.325461ms
      message: 'load-balancer-api-internal: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 4.066247ms
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 11.160084ms
      message: 'load-balancer-api-internal: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 5.124851ms
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 8.442763ms
      message: 'load-balancer-api-internal: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 5.019157ms
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 9.044148ms
      message: 'load-balancer-api-internal: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 4.462313ms
      message: 'load-balancer-api-internal: tcp connection to a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 8.886877ms
      message: 'load-balancer-api-internal: resolved host name a3be1466c4e88431788245431b6a1f76-dfe4ff40ca482669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:30:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-network-check-target-ip-10-0-135-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32627"
    uid: ac20d6f5-c023-4c64-a9de-ec6a16e5dd9f
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:10Z"
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332682ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 2.20347ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 2.292173ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 2.536594ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 2.307536ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 2.588091ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:29:10Z"
    - latency: 2.374386ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:28:10Z"
    - latency: 2.364142ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:27:10Z"
    - latency: 2.556256ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:26:10Z"
    - latency: 2.432008ms
      message: 'network-check-target-ip-10-0-135-216: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-network-check-target-ip-10-0-136-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32626"
    uid: 2ad4017e-67dc-4353-a5be-f1f7a51384e6
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:10Z"
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.010595ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 2.122013ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 2.109458ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 2.116427ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 2.246529ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 3.35585ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:29:10Z"
    - latency: 2.325211ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:28:10Z"
    - latency: 2.681588ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:27:10Z"
    - latency: 2.9161ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:26:10Z"
    - latency: 2.368643ms
      message: 'network-check-target-ip-10-0-136-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-network-check-target-ip-10-0-143-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32624"
    uid: 31bd5ad8-ea43-46f9-bb51-edd4d065b029
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:59:10Z"
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.495µs
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 856.674µs
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 1.338232ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 970.79µs
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 1.41751ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 1.314317ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:29:10Z"
    - latency: 1.494551ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:28:10Z"
    - latency: 894.922µs
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:27:10Z"
    - latency: 1.000784ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:26:10Z"
    - latency: 1.218617ms
      message: 'network-check-target-ip-10-0-143-167: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:25:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T14:52:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-167-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-167.ec2.internal
      uid: 35a3ebdc-2ccd-4f8a-92fe-c740258e57de
    resourceVersion: "32625"
    uid: 202bfc28-0d2f-4ecc-b4ad-21825e8d393a
  spec:
    sourcePod: network-check-source-65bdbbff45-6frvt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T14:58:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.216µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 1.674312ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:34:10Z"
    - latency: 993.435µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 1.716872ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:33:10Z"
    - latency: 1.011158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 1.92922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:32:10Z"
    - latency: 819.62µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 1.886599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:31:10Z"
    - latency: 1.120369ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T15:30:10Z"
    - latency: 1.709387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T15:30:10Z"
kind: List
metadata:
  resourceVersion: ""