apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "75494"
    uid: 4a700bcf-bcc0-424f-97f6-470e9f99501c
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.168024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:20Z"
    - latency: 1.102423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:20Z"
    - latency: 986.697µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:20Z"
    - latency: 798.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 1.160505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 1.08215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 1.191881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 1.145661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 993.813µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:20Z"
    - latency: 6.273234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "72048"
    uid: 2af0699a-108c-4729-b725-da416ad3f03f
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:20Z"
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.242047ms
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 8.193781ms
      message: 'load-balancer-api-external: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 5.510796ms
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 10.34143ms
      message: 'load-balancer-api-external: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 5.658694ms
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 7.534154ms
      message: 'load-balancer-api-external: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 6.389662ms
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 8.825096ms
      message: 'load-balancer-api-external: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 4.982672ms
      message: 'load-balancer-api-external: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 9.813084ms
      message: 'load-balancer-api-external: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "72047"
    uid: 15dfe85a-9682-46c6-a1e7-ca475494f85e
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:20Z"
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.204343ms
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 8.244575ms
      message: 'load-balancer-api-internal: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 5.544683ms
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 10.279787ms
      message: 'load-balancer-api-internal: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 6.383587ms
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 7.432065ms
      message: 'load-balancer-api-internal: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 10.291139ms
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 8.73442ms
      message: 'load-balancer-api-internal: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 4.935974ms
      message: 'load-balancer-api-internal: tcp connection to a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 9.869167ms
      message: 'load-balancer-api-internal: resolved host name a82e8d244855f44cba1b5ffa6154dda1-e7a1ace1f52dd6f2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:34:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-network-check-target-ip-10-0-128-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "75493"
    uid: c130dc46-eefa-45c0-9823-de96b515daa4
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:20Z"
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.430858ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:20Z"
    - latency: 2.870431ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:20Z"
    - latency: 2.370548ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:20Z"
    - latency: 2.330402ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 2.512724ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 2.422409ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 2.504369ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 2.400469ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 2.437331ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:20Z"
    - latency: 6.392348ms
      message: 'network-check-target-ip-10-0-128-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-network-check-target-ip-10-0-133-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "75491"
    uid: fabcbc36-e826-4443-af9c-eff19d259207
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:20Z"
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.635µs
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:20Z"
    - latency: 1.598269ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:20Z"
    - latency: 1.137437ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:20Z"
    - latency: 958.869µs
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 984.673µs
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 949.974µs
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 1.232601ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 1.594859ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 1.378028ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:20Z"
    - latency: 6.813856ms
      message: 'network-check-target-ip-10-0-133-194: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-network-check-target-ip-10-0-135-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "75492"
    uid: 9743deeb-2337-43be-9782-957233349c41
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:45:20Z"
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.108689ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:41:20Z"
    - latency: 2.489661ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:40:20Z"
    - latency: 2.070186ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:39:20Z"
    - latency: 1.817973ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 2.2066ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 2.337745ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 2.255098ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 2.253183ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 2.081386ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:33:20Z"
    - latency: 6.608828ms
      message: 'network-check-target-ip-10-0-135-84: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:32:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:38:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-194-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-194.ec2.internal
      uid: ee9b17aa-1c07-4633-a949-d80c911d960c
    resourceVersion: "72045"
    uid: ef171b05-81d6-4662-bf7e-759a5204d71a
  spec:
    sourcePod: network-check-source-7cbc45fddc-cq2fr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:44:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.329306ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 1.603557ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:38:20Z"
    - latency: 936.817µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 1.732708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:37:20Z"
    - latency: 1.46936ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 1.774456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:36:20Z"
    - latency: 1.049863ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 2.234455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:35:20Z"
    - latency: 1.111127ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:34:20Z"
    - latency: 1.931937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:34:20Z"
kind: List
metadata:
  resourceVersion: ""