apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71466"
    uid: 84f76bd3-cddf-4d27-b439-17b899bb8f19
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:54:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 1.162291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 994.45µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 1.462042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 1.310239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 1.03499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:24:46Z"
    - latency: 1.097838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:23:46Z"
    - latency: 1.057159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:22:46Z"
    - latency: 1.274216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:21:46Z"
    - latency: 1.604168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71468"
    uid: 6688c31e-53be-456d-a1bb-4e99504d9639
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:53:46Z"
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.256214ms
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 8.059314ms
      message: 'load-balancer-api-external: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 6.122414ms
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 8.614662ms
      message: 'load-balancer-api-external: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 5.139971ms
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 14.803431ms
      message: 'load-balancer-api-external: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 5.41754ms
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 7.154661ms
      message: 'load-balancer-api-external: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 4.95003ms
      message: 'load-balancer-api-external: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 7.52718ms
      message: 'load-balancer-api-external: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:25:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71469"
    uid: 6ef8268b-d02c-4615-9ee4-0f473d5dcf23
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:53:46Z"
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.17966ms
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 8.09349ms
      message: 'load-balancer-api-internal: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 5.203527ms
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 8.631099ms
      message: 'load-balancer-api-internal: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 5.110794ms
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 14.841876ms
      message: 'load-balancer-api-internal: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 5.459843ms
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 7.182354ms
      message: 'load-balancer-api-internal: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 4.905733ms
      message: 'load-balancer-api-internal: tcp connection to ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 7.55834ms
      message: 'load-balancer-api-internal: resolved host name ab1d0729a51fc430593d632c2eade89b-089437cdf69ef1c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:25:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-network-check-target-ip-10-0-131-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71464"
    uid: 99143024-b06c-48e7-8cd5-fb02536ec38c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:54:46Z"
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.191879ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 2.196847ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 2.341273ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 2.488892ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 2.110169ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 2.396983ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:24:46Z"
    - latency: 2.932978ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:23:46Z"
    - latency: 2.402863ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:22:46Z"
    - latency: 2.468446ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:21:46Z"
    - latency: 2.381613ms
      message: 'network-check-target-ip-10-0-131-244: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-network-check-target-ip-10-0-137-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71462"
    uid: 10a7d432-ddb2-4e9c-ba5c-d3cf13f6a45c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:54:46Z"
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.379407ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 1.277385ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 938.084µs
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 839.308µs
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 956.439µs
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 1.238817ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:24:46Z"
    - latency: 1.280423ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:23:46Z"
    - latency: 994.136µs
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:22:46Z"
    - latency: 1.002141ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:21:46Z"
    - latency: 1.251437ms
      message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-network-check-target-ip-10-0-139-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71463"
    uid: c166ad50-5517-46fb-a448-7476ff013371
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:54:46Z"
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.172091ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 1.852917ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 1.974878ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 1.930467ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 1.853267ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 1.959014ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:24:46Z"
    - latency: 2.264288ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:23:46Z"
    - latency: 2.316826ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:22:46Z"
    - latency: 2.00829ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:21:46Z"
    - latency: 2.108056ms
      message: 'network-check-target-ip-10-0-139-151: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:20:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T17:47:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-82.ec2.internal
      uid: a578998a-da75-4009-9c29-cb45f52e4317
    resourceVersion: "71465"
    uid: 5762b267-eef4-4057-84c3-3c36713a891b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-grgvm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T17:53:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016496ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 2.131298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:29:46Z"
    - latency: 876.21µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 2.047184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:28:46Z"
    - latency: 891.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 1.997329ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:27:46Z"
    - latency: 1.030032ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 1.955716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:26:46Z"
    - latency: 976.241µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:25:46Z"
    - latency: 1.813627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:25:46Z"
kind: List
metadata:
  resourceVersion: ""