apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "55106"
    uid: 46bd912b-2ef2-4cdc-bbac-db1b3177f68f
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:35:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 1.278338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 1.241258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 1.651038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 1.302303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 1.354671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 1.212208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.602147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.773074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 1.341295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "56243"
    uid: f11eb1ff-347f-41bc-a0e2-c1d2af381611
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:34:10Z"
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.939167ms
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 11.847224ms
      message: 'load-balancer-api-external: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 4.476724ms
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 8.133119ms
      message: 'load-balancer-api-external: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 4.634483ms
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 7.611547ms
      message: 'load-balancer-api-external: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 4.60714ms
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 7.788179ms
      message: 'load-balancer-api-external: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 4.834961ms
      message: 'load-balancer-api-external: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 8.008804ms
      message: 'load-balancer-api-external: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "56242"
    uid: 76e04143-ef6e-466f-97f0-60d804d9d704
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:34:10Z"
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.881702ms
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 11.822303ms
      message: 'load-balancer-api-internal: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 5.432481ms
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 8.250236ms
      message: 'load-balancer-api-internal: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 4.68659ms
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 7.568126ms
      message: 'load-balancer-api-internal: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 4.625689ms
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 7.731677ms
      message: 'load-balancer-api-internal: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 4.810332ms
      message: 'load-balancer-api-internal: tcp connection to ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 8.025795ms
      message: 'load-balancer-api-internal: resolved host name ac4015802368643e2b007ed0df4a1a97-f829f39f1594f79c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:00:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-network-check-target-ip-10-0-133-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "55104"
    uid: 0d8dd72e-3d13-4a42-98e6-8cf089f97da4
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:35:10Z"
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.926306ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 2.191805ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 2.215773ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 2.485062ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 2.173158ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 2.02709ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 2.0749ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.878356ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 2.013754ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 2.162352ms
      message: 'network-check-target-ip-10-0-133-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-network-check-target-ip-10-0-138-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "55103"
    uid: a5f904c2-817d-483a-a9ef-662e6b431e53
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:35:10Z"
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020211ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 984.084µs
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 1.289152ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 1.121782ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 1.440399ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 1.353343ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 1.058856ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 1.244788ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 1.196285ms
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 999.986µs
      message: 'network-check-target-ip-10-0-138-135: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-network-check-target-ip-10-0-139-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "55105"
    uid: 76a53be2-5cc0-43fc-8156-29e2ab2f7091
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:35:10Z"
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.306163ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 2.315187ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 2.419131ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 2.532933ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 2.316479ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:59:10Z"
    - latency: 2.529036ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:58:10Z"
    - latency: 2.226776ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:57:10Z"
    - latency: 2.438356ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:56:10Z"
    - latency: 2.469666ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:55:10Z"
    - latency: 2.330745ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:54:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:28:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-135-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-135.ec2.internal
      uid: 7077a7a8-9813-487c-8abb-367b57f07ce4
    resourceVersion: "56241"
    uid: 91b02371-9445-4683-ae40-9f02a6290602
  spec:
    sourcePod: network-check-source-989f8b8dc-rl8k8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:34:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 1.787245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:04:10Z"
    - latency: 1.00893ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 2.152628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:03:10Z"
    - latency: 1.09885ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 2.106772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:02:10Z"
    - latency: 1.019937ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 2.066147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:01:10Z"
    - latency: 1.403966ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:00:10Z"
    - latency: 2.061956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:00:10Z"
kind: List
metadata:
  resourceVersion: ""