apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "58758"
    uid: 74830168-105f-4405-a959-573aa8d5513b
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:42:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.188789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:10:50Z"
    - latency: 980.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:50Z"
    - latency: 1.239302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:50Z"
    - latency: 1.41468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:50Z"
    - latency: 1.818447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:50Z"
    - latency: 865.464µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 998.913µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 916.66µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 1.07914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 1.187177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "54437"
    uid: dfa5ce48-cc57-43fa-ab01-f9d7a1ed28b7
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:50Z"
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.16529ms
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 9.538917ms
      message: 'load-balancer-api-external: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 5.739817ms
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 6.830221ms
      message: 'load-balancer-api-external: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 5.354936ms
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 6.873599ms
      message: 'load-balancer-api-external: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 5.350597ms
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 6.764979ms
      message: 'load-balancer-api-external: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 7.493336ms
      message: 'load-balancer-api-external: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
    - latency: 6.701094ms
      message: 'load-balancer-api-external: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "54438"
    uid: 91d23c49-73c6-459f-b61e-657eb13b071f
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:50Z"
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.156426ms
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 9.585794ms
      message: 'load-balancer-api-internal: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 5.702424ms
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 6.89515ms
      message: 'load-balancer-api-internal: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 5.354163ms
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 6.787367ms
      message: 'load-balancer-api-internal: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 5.37032ms
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 6.861179ms
      message: 'load-balancer-api-internal: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 7.507265ms
      message: 'load-balancer-api-internal: tcp connection to af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
    - latency: 6.771623ms
      message: 'load-balancer-api-internal: resolved host name af703b452e50042e4af4fdb7ec5e11ed-95d25cedbae94d36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-133-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "58757"
    uid: 70b8ae27-95a0-4521-bc2d-b8d600186769
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:42:50Z"
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.477975ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:10:50Z"
    - latency: 2.118271ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:50Z"
    - latency: 2.469625ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:50Z"
    - latency: 2.191918ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:50Z"
    - latency: 2.24315ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:50Z"
    - latency: 1.963159ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 2.450474ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 2.498604ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 2.7017ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 2.169551ms
      message: 'network-check-target-ip-10-0-133-48: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-139-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "58755"
    uid: 8f60aed9-f9fc-4122-a71c-904264c634b8
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:42:50Z"
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.443947ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:10:50Z"
    - latency: 965.481µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:50Z"
    - latency: 1.004113ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:50Z"
    - latency: 907.644µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:50Z"
    - latency: 855.801µs
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:50Z"
    - latency: 1.378036ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 1.317626ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 1.235291ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 1.012655ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 1.046268ms
      message: 'network-check-target-ip-10-0-139-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-ip-10-0-140-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "58756"
    uid: 29eb5466-29db-4cbd-aeb6-e5ae123910dc
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:42:50Z"
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.266448ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:10:50Z"
    - latency: 2.490322ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:09:50Z"
    - latency: 2.429323ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:08:50Z"
    - latency: 2.226292ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:07:50Z"
    - latency: 2.894217ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:06:50Z"
    - latency: 1.929577ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 2.266104ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 2.454608ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 2.386321ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 2.44031ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:35:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-172.ec2.internal
      uid: 492286e0-8264-4092-b556-fd8a4a1d2378
    resourceVersion: "54436"
    uid: e94e6b31-e87b-43f2-b3b8-2f895b0c1d5d
  spec:
    sourcePod: network-check-source-685456655f-2kfkp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:41:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015328ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 1.790197ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:05:50Z"
    - latency: 938.629µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 2.166524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:04:50Z"
    - latency: 849.999µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 1.764886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:03:50Z"
    - latency: 1.089988ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 1.674316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:02:50Z"
    - latency: 1.234712ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T14:01:50Z"
    - latency: 1.964329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T14:01:50Z"
kind: List
metadata:
  resourceVersion: ""