apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "39305"
    uid: aac0991f-4f77-454d-a51a-b25a2ed6bd7f
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.826µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:09Z"
    - latency: 1.412966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 1.113643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 1.101074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 1.083753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 905.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 1.449608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:32:09Z"
    - latency: 845.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:31:09Z"
    - latency: 992.038µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:30:09Z"
    - latency: 1.053415ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "38758"
    uid: 85f6b66b-0fb5-44c2-8520-4cebf489f0fd
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:09Z"
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.732035ms
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 7.720081ms
      message: 'load-balancer-api-external: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 4.366871ms
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 7.487404ms
      message: 'load-balancer-api-external: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 4.838848ms
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 6.950492ms
      message: 'load-balancer-api-external: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 4.471057ms
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 7.167027ms
      message: 'load-balancer-api-external: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 4.102225ms
      message: 'load-balancer-api-external: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 6.300052ms
      message: 'load-balancer-api-external: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:33:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "38757"
    uid: 8f406430-27bc-4331-b60f-159ba5a8997b
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:09Z"
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.701005ms
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 7.756715ms
      message: 'load-balancer-api-internal: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 4.121851ms
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 7.557753ms
      message: 'load-balancer-api-internal: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 4.83398ms
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 6.920928ms
      message: 'load-balancer-api-internal: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 4.493198ms
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 7.131112ms
      message: 'load-balancer-api-internal: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 4.069259ms
      message: 'load-balancer-api-internal: tcp connection to a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 6.334812ms
      message: 'load-balancer-api-internal: resolved host name a205c47fa6bb141d8b518256ca08493c-9b645362fc9455d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:33:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-network-check-target-ip-10-0-136-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "39303"
    uid: a4822842-157d-459f-8356-df25391d5d2e
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:09Z"
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.132407ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:09Z"
    - latency: 2.267522ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 1.991366ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 1.979885ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 2.156448ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 2.134926ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 1.915207ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:32:09Z"
    - latency: 1.879269ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:31:09Z"
    - latency: 2.032324ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:30:09Z"
    - latency: 1.951929ms
      message: 'network-check-target-ip-10-0-136-174: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-network-check-target-ip-10-0-137-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "39304"
    uid: 87bf6382-a640-404d-b407-26a8909bc492
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:09Z"
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.434472ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:09Z"
    - latency: 2.26765ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 2.454072ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 2.196202ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 2.419912ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 2.255341ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 2.317755ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:32:09Z"
    - latency: 2.036809ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:31:09Z"
    - latency: 2.28565ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:30:09Z"
    - latency: 2.346605ms
      message: 'network-check-target-ip-10-0-137-252: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-network-check-target-ip-10-0-140-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "39302"
    uid: 2cf4eda5-c2c7-4a9b-9962-66478666df02
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:56:09Z"
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 867.258µs
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:09Z"
    - latency: 1.620858ms
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 925.709µs
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 954.56µs
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 838.87µs
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 1.49976ms
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 1.049508ms
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:32:09Z"
    - latency: 1.509483ms
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:31:09Z"
    - latency: 1.640926ms
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:30:09Z"
    - latency: 994.878µs
      message: 'network-check-target-ip-10-0-140-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:29:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:49:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-138-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-138.ec2.internal
      uid: 46e8971d-fd02-4906-b22e-9f9b86462cc9
    resourceVersion: "38755"
    uid: 56cf578a-5572-40f5-a24b-bad3e31d2c7f
  spec:
    sourcePod: network-check-source-65bdbbff45-ktsf2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 2.85009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:37:09Z"
    - latency: 997.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 1.851465ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:36:09Z"
    - latency: 1.092763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 1.733749ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:35:09Z"
    - latency: 939.392µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 1.954091ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:34:09Z"
    - latency: 1.078845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:33:09Z"
    - latency: 1.592518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:33:09Z"
kind: List
metadata:
  resourceVersion: ""