apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "22017"
    uid: 6a021d5b-edad-4ec5-920b-413b9a91007d
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:28:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:49:19Z"
    - latency: 1.180462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:48:19Z"
    - latency: 1.124869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:47:19Z"
    - latency: 1.228563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:46:19Z"
    - latency: 919.992µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 917.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 937.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 927.797µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 965.607µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 1.236418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "20168"
    uid: e56234d0-5a5c-4db6-beb4-675967511e31
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:27:19Z"
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.411913ms
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 7.877834ms
      message: 'load-balancer-api-external: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 4.858362ms
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 10.75452ms
      message: 'load-balancer-api-external: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 4.159478ms
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 7.879888ms
      message: 'load-balancer-api-external: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 3.639911ms
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 10.280903ms
      message: 'load-balancer-api-external: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 5.072733ms
      message: 'load-balancer-api-external: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 8.377365ms
      message: 'load-balancer-api-external: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "20167"
    uid: 427c6683-9485-4fde-a854-b0a162463053
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:27:19Z"
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.436637ms
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 8.061933ms
      message: 'load-balancer-api-internal: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 4.490801ms
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 10.783531ms
      message: 'load-balancer-api-internal: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 3.963624ms
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 7.846489ms
      message: 'load-balancer-api-internal: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 4.353239ms
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 10.260572ms
      message: 'load-balancer-api-internal: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 4.929814ms
      message: 'load-balancer-api-internal: tcp connection to a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 8.464706ms
      message: 'load-balancer-api-internal: resolved host name a9485c929f88e43d2a18c6df8c384057-c067597a70fa4147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:41:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-network-check-target-ip-10-0-130-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "22015"
    uid: 184bea8e-9ef8-479a-9620-3293868a2cc4
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:28:19Z"
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.362353ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:49:19Z"
    - latency: 2.186472ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:48:19Z"
    - latency: 2.40023ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:47:19Z"
    - latency: 2.770725ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:46:19Z"
    - latency: 2.206238ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 2.149581ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 1.966332ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 2.331408ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 2.275319ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 2.58632ms
      message: 'network-check-target-ip-10-0-130-43: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-network-check-target-ip-10-0-136-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "22014"
    uid: 0bbf9389-891a-471a-95aa-de59d3f58e2a
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:28:19Z"
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 839.539µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:49:19Z"
    - latency: 1.120701ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:48:19Z"
    - latency: 892.256µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:47:19Z"
    - latency: 796.991µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:46:19Z"
    - latency: 868.832µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 958.687µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 1.192883ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 852.486µs
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 1.010606ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 1.440169ms
      message: 'network-check-target-ip-10-0-136-69: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-network-check-target-ip-10-0-141-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "22016"
    uid: dedf0365-7925-42f6-8319-506ac0d83401
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:28:19Z"
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.762185ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:49:19Z"
    - latency: 2.059438ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:48:19Z"
    - latency: 2.08132ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:47:19Z"
    - latency: 2.559449ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:46:19Z"
    - latency: 2.255354ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 2.207996ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 1.995438ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 1.977954ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 2.34544ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 2.122944ms
      message: 'network-check-target-ip-10-0-141-213: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:40:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T17:21:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-69.ec2.internal
      uid: e398c121-6c33-43bf-9106-01ad3df43ecf
    resourceVersion: "20166"
    uid: 456ae440-10c6-4f26-8db0-4215ce4a1e90
  spec:
    sourcePod: network-check-source-685456655f-rbv4k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T17:27:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 837.591µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 1.834352ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:45:19Z"
    - latency: 1.000178ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 1.657793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:44:19Z"
    - latency: 783.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 1.80184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:43:19Z"
    - latency: 1.136861ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 1.637104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:42:19Z"
    - latency: 850.558µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T17:41:19Z"
    - latency: 1.696442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T17:41:19Z"
kind: List
metadata:
  resourceVersion: ""