apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93235"
    uid: 4663a3e1-2ac4-4ec1-a7f8-5d4bcd3268d4
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:37:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 1.384032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 909.711µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 1.060019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 1.276647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 1.016357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:48Z"
    - latency: 1.135004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:48Z"
    - latency: 980.789µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:48Z"
    - latency: 1.251022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:48Z"
    - latency: 1.007471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93237"
    uid: b11e646b-65d7-4005-8cb7-be6454ca4c3f
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:36:48Z"
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.42791ms
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 7.101734ms
      message: 'load-balancer-api-external: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 13.672161ms
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 6.853432ms
      message: 'load-balancer-api-external: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 3.50667ms
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 6.176873ms
      message: 'load-balancer-api-external: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 4.514329ms
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 11.780883ms
      message: 'load-balancer-api-external: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 3.294355ms
      message: 'load-balancer-api-external: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 6.637858ms
      message: 'load-balancer-api-external: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93238"
    uid: 04d15245-21c1-4880-8616-d436d8712864
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:36:48Z"
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.376354ms
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 7.158879ms
      message: 'load-balancer-api-internal: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 13.684917ms
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 6.886695ms
      message: 'load-balancer-api-internal: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 5.55165ms
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 6.318744ms
      message: 'load-balancer-api-internal: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 5.194549ms
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 11.667137ms
      message: 'load-balancer-api-internal: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 4.850227ms
      message: 'load-balancer-api-internal: tcp connection to a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 6.601766ms
      message: 'load-balancer-api-internal: resolved host name a16f521fd49704d398201909e61fd563-778d758410dab8d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-131-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93233"
    uid: 5f54210a-edff-4fd6-be48-66d9ffc08b1e
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:37:48Z"
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.375µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 809.188µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 850.97µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 865.057µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 1.384131ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 870.339µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:48Z"
    - latency: 1.235419ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:48Z"
    - latency: 913.144µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:48Z"
    - latency: 1.078179ms
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:48Z"
    - latency: 851.492µs
      message: 'network-check-target-ip-10-0-131-165: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-131-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93234"
    uid: 450b6af3-88df-4b5d-9784-40f354106be9
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:37:48Z"
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344043ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 2.504293ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 2.21201ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 2.682746ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 2.80622ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 2.297504ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:48Z"
    - latency: 2.669579ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:48Z"
    - latency: 2.272363ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:48Z"
    - latency: 2.926776ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:48Z"
    - latency: 3.239737ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-ip-10-0-141-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93232"
    uid: 941ef143-2f5d-4cc7-8210-da946c63d843
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:37:48Z"
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250266ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 2.389285ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 2.228835ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 2.256445ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 2.341107ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 2.094819ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:07:48Z"
    - latency: 2.63285ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:06:48Z"
    - latency: 2.257354ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:05:48Z"
    - latency: 2.448805ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:04:48Z"
    - latency: 2.017922ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:03:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:30:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-165.ec2.internal
      uid: b189bd11-ea7f-4d0f-a1cf-b3bb3ccd55c0
    resourceVersion: "93236"
    uid: 439ad016-6051-42be-bf1e-a5bc6b770e47
  spec:
    sourcePod: network-check-source-6f8b768455-zhk4q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:36:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.49092ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 1.778121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:12:48Z"
    - latency: 1.055736ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 1.942627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:11:48Z"
    - latency: 1.274026ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 1.717224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:10:48Z"
    - latency: 1.070488ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 1.94088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:09:48Z"
    - latency: 811.001µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:08:48Z"
    - latency: 1.767717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:08:48Z"
kind: List
metadata:
  resourceVersion: ""