apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31736"
    uid: 0a519f65-4406-4779-9c69-03aa0fc21b97
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.054µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 1.012928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 868.916µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 1.107456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 934.033µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 1.292627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:58:50Z"
    - latency: 864.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:57:50Z"
    - latency: 919.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:56:50Z"
    - latency: 1.07434ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:55:50Z"
    - latency: 1.496825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:54:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31738"
    uid: 301cf763-71b1-4055-9829-439d3ce7e4ee
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:27:50Z"
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.975045ms
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 8.722839ms
      message: 'load-balancer-api-external: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 4.198822ms
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 6.565973ms
      message: 'load-balancer-api-external: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 4.246305ms
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 8.567953ms
      message: 'load-balancer-api-external: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 5.172667ms
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 6.574785ms
      message: 'load-balancer-api-external: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 3.586032ms
      message: 'load-balancer-api-external: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 8.629882ms
      message: 'load-balancer-api-external: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:59:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31737"
    uid: fc9cf249-3430-4138-bb08-9f4ff044c363
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:27:50Z"
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.988923ms
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 8.670405ms
      message: 'load-balancer-api-internal: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 4.194467ms
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 6.599122ms
      message: 'load-balancer-api-internal: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 4.435913ms
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 8.472249ms
      message: 'load-balancer-api-internal: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 4.782616ms
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 6.597432ms
      message: 'load-balancer-api-internal: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 5.534705ms
      message: 'load-balancer-api-internal: tcp connection to ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 8.576944ms
      message: 'load-balancer-api-internal: resolved host name ad0ce3fca5e6643b9af6d6150dc2ccf0-27e1990637acf655.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:59:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-130-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31734"
    uid: f0b3b9d6-8284-4f42-8190-0542f900ad6e
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:50Z"
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.581956ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 2.38427ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 2.351362ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 2.369256ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 2.396801ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 2.309878ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:58:50Z"
    - latency: 2.285306ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:57:50Z"
    - latency: 2.32134ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:56:50Z"
    - latency: 2.162911ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:55:50Z"
    - latency: 2.174848ms
      message: 'network-check-target-ip-10-0-130-121: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:54:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-130-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31735"
    uid: 52f33c69-ed04-4736-8da8-3da1a64f2eba
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:50Z"
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.299413ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 2.284386ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 2.256351ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 2.295234ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 2.395603ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 2.286509ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:58:50Z"
    - latency: 2.196831ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:57:50Z"
    - latency: 1.993127ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:56:50Z"
    - latency: 2.227767ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:55:50Z"
    - latency: 2.199727ms
      message: 'network-check-target-ip-10-0-130-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:54:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-network-check-target-ip-10-0-131-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31732"
    uid: 4ca0ed38-5fc0-4412-b65d-bb442b24109b
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:28:50Z"
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.21849ms
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 845.739µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 820.404µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 893.138µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 872.19µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 1.296814ms
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:58:50Z"
    - latency: 881.599µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:57:50Z"
    - latency: 893.063µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:56:50Z"
    - latency: 810.732µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:55:50Z"
    - latency: 801.995µs
      message: 'network-check-target-ip-10-0-131-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:54:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T21:21:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-12.ec2.internal
      uid: dab2d91f-c3da-446e-b046-3a316b762c8d
    resourceVersion: "31733"
    uid: 4ebb4866-1837-4bb4-89c7-d69251b9db2a
  spec:
    sourcePod: network-check-source-989f8b8dc-7b4gq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T21:27:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 1.552397ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:03:50Z"
    - latency: 969.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 1.820921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:02:50Z"
    - latency: 1.060512ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 1.673997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:01:50Z"
    - latency: 1.022602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 1.737957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T22:00:50Z"
    - latency: 1.076798ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T21:59:50Z"
    - latency: 1.850836ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T21:59:50Z"
kind: List
metadata:
  resourceVersion: ""