apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "54515"
    uid: 2b0b4b32-d07b-4c2e-8705-4cc833499b1b
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:52:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 967.044µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 1.169693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 972.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:33Z"
    - latency: 1.282183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:33Z"
    - latency: 1.09647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:33Z"
    - latency: 1.044253ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:33Z"
    - latency: 1.062211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:33Z"
    - latency: 3.361708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:33Z"
    - latency: 1.056235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "56250"
    uid: b93ae011-636a-49c0-b12f-9a36c892bdc1
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:51:33Z"
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.409737ms
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 7.389358ms
      message: 'load-balancer-api-external: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 5.735066ms
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 7.756097ms
      message: 'load-balancer-api-external: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 4.362889ms
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 6.903639ms
      message: 'load-balancer-api-external: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 5.974621ms
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 7.102375ms
      message: 'load-balancer-api-external: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 8.076718ms
      message: 'load-balancer-api-external: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 6.720444ms
      message: 'load-balancer-api-external: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "56249"
    uid: 88d1045d-b82b-4a9e-b17d-6bae49613f3b
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:51:33Z"
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.395145ms
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 7.426835ms
      message: 'load-balancer-api-internal: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 5.750803ms
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 7.815248ms
      message: 'load-balancer-api-internal: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 4.182736ms
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 6.89372ms
      message: 'load-balancer-api-internal: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 5.949908ms
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 6.989091ms
      message: 'load-balancer-api-internal: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 3.993896ms
      message: 'load-balancer-api-internal: tcp connection to abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 6.678632ms
      message: 'load-balancer-api-internal: resolved host name abb42475ee8b84b9880b86c63bc814ed-d295293b78ae202a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "54514"
    uid: 8e8c65eb-44b1-4bc1-998c-60184f0f7dea
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:52:33Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.853897ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 2.434615ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 2.492171ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 2.704311ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:33Z"
    - latency: 2.528025ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:33Z"
    - latency: 2.39574ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:33Z"
    - latency: 2.688291ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:33Z"
    - latency: 2.820834ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:33Z"
    - latency: 5.175991ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:33Z"
    - latency: 2.722731ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-137-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "54513"
    uid: 32baed54-b98f-4a74-966b-cc9e8943732c
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:52:33Z"
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.748265ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 2.57241ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 2.489475ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 2.488032ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:33Z"
    - latency: 2.316669ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:33Z"
    - latency: 2.857793ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:33Z"
    - latency: 2.205155ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:33Z"
    - latency: 2.456475ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:33Z"
    - latency: 8.056929ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:33Z"
    - latency: 2.508122ms
      message: 'network-check-target-ip-10-0-137-189: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-ip-10-0-139-221
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "54512"
    uid: 480c2fa7-c39b-48c2-8ce5-9b367b6557e7
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:52:33Z"
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.148µs
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 925.006µs
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 888.121µs
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 1.785902ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:10:33Z"
    - latency: 1.041972ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:09:33Z"
    - latency: 1.100071ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:08:33Z"
    - latency: 1.122252ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:07:33Z"
    - latency: 1.735822ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:06:33Z"
    - latency: 1.611282ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:05:33Z"
    - latency: 1.192989ms
      message: 'network-check-target-ip-10-0-139-221: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:04:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T21:45:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-221-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-221.ec2.internal
      uid: 6b610fd7-34da-43fc-b6d2-ed882873e1d1
    resourceVersion: "56246"
    uid: 0faa0a77-1926-4331-ac70-46899fe2dc2a
  spec:
    sourcePod: network-check-source-685456655f-mtj6v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:51:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 1.673516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:15:33Z"
    - latency: 947.604µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 1.820743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:14:33Z"
    - latency: 944.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 1.967084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:13:33Z"
    - latency: 1.2328ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 1.953595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:12:33Z"
    - latency: 864.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T22:11:33Z"
    - latency: 1.739482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T22:11:33Z"
kind: List
metadata:
  resourceVersion: ""