apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63158"
    uid: cc299852-e95c-4fd7-8204-c488364f7230
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:12:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.616µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 1.384908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 1.418383ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 1.263769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 1.245451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 1.360784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:56Z"
    - latency: 1.255763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:56Z"
    - latency: 1.589179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:56Z"
    - latency: 1.523357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:56Z"
    - latency: 1.178682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63159"
    uid: 82b0e90c-820d-47cc-9cf1-9be508db979a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:56Z"
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.615519ms
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 7.92168ms
      message: 'load-balancer-api-external: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 5.558831ms
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 8.956591ms
      message: 'load-balancer-api-external: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 4.267091ms
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 7.752787ms
      message: 'load-balancer-api-external: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 4.68384ms
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 8.486136ms
      message: 'load-balancer-api-external: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 5.126216ms
      message: 'load-balancer-api-external: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 7.658643ms
      message: 'load-balancer-api-external: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63160"
    uid: b8745b7f-1e96-408b-8545-046e8f0a548f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:56Z"
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.859663ms
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 7.842737ms
      message: 'load-balancer-api-internal: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 5.569507ms
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 8.874756ms
      message: 'load-balancer-api-internal: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 4.537879ms
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 7.653291ms
      message: 'load-balancer-api-internal: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 4.972902ms
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 8.523544ms
      message: 'load-balancer-api-internal: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 5.136278ms
      message: 'load-balancer-api-internal: tcp connection to a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 7.533137ms
      message: 'load-balancer-api-internal: resolved host name a763fbb5d8bcf44c0b5a08b95ac6b7d4-15af550afb3530f7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-network-check-target-ip-10-0-134-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63156"
    uid: f43f313f-a5d9-4d92-8241-804692068f49
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:12:56Z"
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.336088ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 5.469326ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 2.466208ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 2.335611ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 2.259352ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 2.368612ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:56Z"
    - latency: 2.644731ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:56Z"
    - latency: 2.688247ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:56Z"
    - latency: 2.405064ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:56Z"
    - latency: 2.462668ms
      message: 'network-check-target-ip-10-0-134-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-network-check-target-ip-10-0-137-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63155"
    uid: eeec5efc-3923-4248-8720-73fefefa0f49
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:12:56Z"
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.257424ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 2.355329ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 2.460208ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 2.349913ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 1.990501ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 2.207492ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:56Z"
    - latency: 3.126425ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:56Z"
    - latency: 2.59524ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:56Z"
    - latency: 2.580626ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:56Z"
    - latency: 2.384124ms
      message: 'network-check-target-ip-10-0-137-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-network-check-target-ip-10-0-143-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63154"
    uid: 1afe78b5-6bd8-4a64-bb24-ecf3f8c3e9f5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:12:56Z"
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.497222ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 1.432946ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 1.024704ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 1.056676ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 867.823µs
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 1.074842ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:42:56Z"
    - latency: 1.671178ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:41:56Z"
    - latency: 887.549µs
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:40:56Z"
    - latency: 1.663524ms
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:39:56Z"
    - latency: 979.928µs
      message: 'network-check-target-ip-10-0-143-41: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:38:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T18:05:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-41.ec2.internal
      uid: 7a4bece2-1adb-487c-87c9-74df08359494
    resourceVersion: "63157"
    uid: e8d25001-8aca-4bbc-975b-54f8da1fd0ea
  spec:
    sourcePod: network-check-source-7bc5b6bf85-wq2tn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T18:11:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.229602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 2.325409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:47:56Z"
    - latency: 1.183734ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 2.052853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:46:56Z"
    - latency: 1.367433ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 2.323411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:45:56Z"
    - latency: 1.073292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 1.89445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:44:56Z"
    - latency: 1.02373ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T18:43:56Z"
    - latency: 2.313358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T18:43:56Z"
kind: List
metadata:
  resourceVersion: ""