apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "76872"
    uid: 3685b21f-8870-4a33-bb01-2db1186cd09b
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:35:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.739µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 1.075455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:23:46Z"
    - latency: 839.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:22:46Z"
    - latency: 995.886µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:21:46Z"
    - latency: 1.044903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:20:46Z"
    - latency: 1.004831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:19:46Z"
    - latency: 1.00708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:18:46Z"
    - latency: 994.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:17:46Z"
    - latency: 1.237329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:16:46Z"
    - latency: 1.465629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "81095"
    uid: c8e6dc88-be07-4495-9328-fcbeb56b13dc
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:34:46Z"
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.152201ms
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 10.471638ms
      message: 'load-balancer-api-external: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 5.240499ms
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 9.260417ms
      message: 'load-balancer-api-external: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 4.901082ms
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 9.109829ms
      message: 'load-balancer-api-external: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 4.644681ms
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 7.189937ms
      message: 'load-balancer-api-external: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 4.015609ms
      message: 'load-balancer-api-external: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 8.733034ms
      message: 'load-balancer-api-external: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:24:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "81096"
    uid: bd981d9b-d8e5-4c0a-8b3f-50fdc79bf044
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:34:46Z"
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.603352ms
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 10.494917ms
      message: 'load-balancer-api-internal: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 5.048065ms
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 9.29279ms
      message: 'load-balancer-api-internal: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 4.238604ms
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 9.210234ms
      message: 'load-balancer-api-internal: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 4.640168ms
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 7.217309ms
      message: 'load-balancer-api-internal: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 4.537154ms
      message: 'load-balancer-api-internal: tcp connection to a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 8.757632ms
      message: 'load-balancer-api-internal: resolved host name a4380fa5c2d7341a0896cce924485d25-89588d810afa744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:24:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-128-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "76869"
    uid: cfc774c4-9b62-468a-bd13-316abea3c475
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:35:46Z"
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.552µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 1.003818ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:23:46Z"
    - latency: 892.025µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:22:46Z"
    - latency: 876.661µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:21:46Z"
    - latency: 949.162µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:20:46Z"
    - latency: 943.398µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:19:46Z"
    - latency: 935.323µs
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:18:46Z"
    - latency: 1.231973ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:17:46Z"
    - latency: 1.406676ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:16:46Z"
    - latency: 1.202309ms
      message: 'network-check-target-ip-10-0-128-25: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-137-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "76870"
    uid: 3be640ea-7ae8-4d56-932e-fe8228161d47
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:35:46Z"
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.486692ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 1.987431ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:23:46Z"
    - latency: 1.967993ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:22:46Z"
    - latency: 2.283227ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:21:46Z"
    - latency: 2.420549ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:20:46Z"
    - latency: 2.41915ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:19:46Z"
    - latency: 2.470579ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:18:46Z"
    - latency: 2.420379ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:17:46Z"
    - latency: 2.139955ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:16:46Z"
    - latency: 2.49371ms
      message: 'network-check-target-ip-10-0-137-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-ip-10-0-142-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "76871"
    uid: c73db14e-5c33-49c1-969f-2282732730d1
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:35:46Z"
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.682962ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 1.987166ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:23:46Z"
    - latency: 2.140429ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:22:46Z"
    - latency: 2.633854ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:21:46Z"
    - latency: 2.233193ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:20:46Z"
    - latency: 2.067692ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:19:46Z"
    - latency: 2.481311ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:18:46Z"
    - latency: 2.36835ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:17:46Z"
    - latency: 2.41962ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:16:46Z"
    - latency: 2.527491ms
      message: 'network-check-target-ip-10-0-142-162: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:15:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T12:28:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-25-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-25.ec2.internal
      uid: 19133362-96c0-4141-ac15-0e044048c165
    resourceVersion: "81094"
    uid: 778b230a-a260-4ac3-910a-2939bb715b1a
  spec:
    sourcePod: network-check-source-7d88cb55d8-vwjkc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T12:34:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018947ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 2.605089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:28:46Z"
    - latency: 1.16568ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 2.021419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:27:46Z"
    - latency: 1.194757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 1.89783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:26:46Z"
    - latency: 978.181µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 2.405334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:25:46Z"
    - latency: 1.18797ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T13:24:46Z"
    - latency: 1.825877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T13:24:46Z"
kind: List
metadata:
  resourceVersion: ""