apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "22537"
    uid: 3d0b5aa0-eaa7-47f7-b1fe-6fda3f9757e6
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:32:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.150879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:53:30Z"
    - latency: 905.945µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:52:30Z"
    - latency: 835.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:51:30Z"
    - latency: 846.118µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:50:30Z"
    - latency: 915.115µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 889.682µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 983.265µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 896.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 1.019478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "20711"
    uid: c2e06245-6723-4288-9322-95bafdc542dc
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:31:30Z"
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.788406ms
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 7.020776ms
      message: 'load-balancer-api-external: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 4.943862ms
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 8.242304ms
      message: 'load-balancer-api-external: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 4.815354ms
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 8.280412ms
      message: 'load-balancer-api-external: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 8.307135ms
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 6.950509ms
      message: 'load-balancer-api-external: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 3.721887ms
      message: 'load-balancer-api-external: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 8.413983ms
      message: 'load-balancer-api-external: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "20712"
    uid: d3245d7f-7089-4d69-ad0c-cca1d6cacc4e
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:31:30Z"
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.763369ms
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 7.133498ms
      message: 'load-balancer-api-internal: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 4.821532ms
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 8.164173ms
      message: 'load-balancer-api-internal: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 4.827174ms
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 8.243555ms
      message: 'load-balancer-api-internal: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 8.311018ms
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 6.902049ms
      message: 'load-balancer-api-internal: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 4.123175ms
      message: 'load-balancer-api-internal: tcp connection to ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 8.360192ms
      message: 'load-balancer-api-internal: resolved host name ae884b87a10dd4ed888fb94cb5aa6e21-6774caac4cbd6aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-131-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "22536"
    uid: 9f4231ff-8c45-485b-b675-1f1348859d57
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:32:30Z"
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.439199ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:53:30Z"
    - latency: 829.106µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:52:30Z"
    - latency: 1.096359ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:51:30Z"
    - latency: 1.268836ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:50:30Z"
    - latency: 836.043µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 858.348µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 1.410433ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 991.638µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 734.077µs
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 1.165914ms
      message: 'network-check-target-ip-10-0-131-105: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-132-17
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "22534"
    uid: 77353146-37ea-40c7-84d8-91194880dd6f
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:32:30Z"
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.169715ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:53:30Z"
    - latency: 1.813422ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:52:30Z"
    - latency: 2.39598ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:51:30Z"
    - latency: 2.329106ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:50:30Z"
    - latency: 2.032311ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 2.705784ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 2.420696ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 2.219597ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 2.55329ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 2.217977ms
      message: 'network-check-target-ip-10-0-132-17: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-ip-10-0-141-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "22535"
    uid: 8db0c32d-a27c-45ae-9e93-74a0b2c2a477
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:32:30Z"
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.403502ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:53:30Z"
    - latency: 2.42111ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:52:30Z"
    - latency: 2.312269ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:51:30Z"
    - latency: 2.607213ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:50:30Z"
    - latency: 2.378106ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 2.162149ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 2.390905ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 2.229498ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 2.191129ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 2.583334ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:44:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T07:25:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-105.ec2.internal
      uid: a1051b70-a71f-4449-b0fe-e6a085a05ee6
    resourceVersion: "20710"
    uid: 0a48e985-eefd-49fb-9baa-7640bf2ca62e
  spec:
    sourcePod: network-check-source-6f8b768455-jczcf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T07:31:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 923.106µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 1.567471ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:49:30Z"
    - latency: 938.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 1.905677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:48:30Z"
    - latency: 1.086867ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 1.676944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:47:30Z"
    - latency: 1.202394ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 1.872237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:46:30Z"
    - latency: 858.713µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T07:45:30Z"
    - latency: 2.936104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T07:45:30Z"
kind: List
metadata:
  resourceVersion: ""