apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31658"
    uid: 49838e42-15a6-4a61-9dc4-e14e6f01e422
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 964.196µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 1.116154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 1.065544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 858.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 1.047889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:33:30Z"
    - latency: 1.02862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:32:30Z"
    - latency: 993.822µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:31:30Z"
    - latency: 1.072635ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:30:30Z"
    - latency: 799.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:29:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31660"
    uid: e116bea1-21a7-4908-a9b5-c75ce64598ad
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:30Z"
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.030403ms
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 7.513852ms
      message: 'load-balancer-api-external: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 4.128083ms
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 7.966113ms
      message: 'load-balancer-api-external: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 4.78061ms
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 7.538716ms
      message: 'load-balancer-api-external: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 5.458754ms
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 8.076879ms
      message: 'load-balancer-api-external: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 4.654791ms
      message: 'load-balancer-api-external: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 7.515802ms
      message: 'load-balancer-api-external: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:34:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31659"
    uid: 799f2d46-7b12-482d-ae46-4b2e16c0389c
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:30Z"
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.036254ms
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 7.385168ms
      message: 'load-balancer-api-internal: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 4.136591ms
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 8.001643ms
      message: 'load-balancer-api-internal: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 4.746293ms
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 7.608712ms
      message: 'load-balancer-api-internal: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 4.045623ms
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 8.0052ms
      message: 'load-balancer-api-internal: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 4.120059ms
      message: 'load-balancer-api-internal: tcp connection to a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 7.500428ms
      message: 'load-balancer-api-internal: resolved host name a0ced950990a5452abda2d0f66e1b6c1-8cb4aaa9cd7fe542.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:34:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-129-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31656"
    uid: 9121e793-d9f9-407e-aefc-e81ede2052fc
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:30Z"
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.193106ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 2.170699ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 2.339318ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 2.29914ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 2.210739ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 2.398531ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:33:30Z"
    - latency: 2.189662ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:32:30Z"
    - latency: 2.525627ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:31:30Z"
    - latency: 2.0252ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:30:30Z"
    - latency: 2.006576ms
      message: 'network-check-target-ip-10-0-129-98: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:29:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-135-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31654"
    uid: 0faabf12-b8bc-4eb6-9072-7e88af2a1710
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:30Z"
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 822.58µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 821.256µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 1.215146ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 1.289049ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 1.246254ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 922.301µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:33:30Z"
    - latency: 1.016623ms
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:32:30Z"
    - latency: 871.378µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:31:30Z"
    - latency: 863.207µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:30:30Z"
    - latency: 871.243µs
      message: 'network-check-target-ip-10-0-135-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:29:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-ip-10-0-142-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31655"
    uid: 5a190a30-b4c9-4758-808d-8f5aa54aa6af
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:03:30Z"
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315957ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 2.316532ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 2.281763ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 2.125789ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 1.980892ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 2.043602ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:33:30Z"
    - latency: 2.231459ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:32:30Z"
    - latency: 2.198104ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:31:30Z"
    - latency: 2.246787ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:30:30Z"
    - latency: 1.903857ms
      message: 'network-check-target-ip-10-0-142-30: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:29:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T23:56:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-201.ec2.internal
      uid: 18e18b8e-1015-4a57-937d-f557241c2aee
    resourceVersion: "31657"
    uid: 1632d763-e60e-41e6-98e4-556a05b94094
  spec:
    sourcePod: network-check-source-8894fc9bd-s5dsn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-25T00:02:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020874ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 1.666203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:38:30Z"
    - latency: 731.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 1.784463ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:37:30Z"
    - latency: 680.643µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 1.785965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:36:30Z"
    - latency: 1.000864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 1.733032ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:35:30Z"
    - latency: 921.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-25T00:34:30Z"
    - latency: 1.706416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-25T00:34:30Z"
kind: List
metadata:
  resourceVersion: ""