apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "58338"
    uid: a4ebdd3a-4b79-49ec-8e1b-0ad0bb8f068f
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:31:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.353057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 1.147182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 917.568µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 930.286µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:15Z"
    - latency: 1.261308ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:15Z"
    - latency: 1.096878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:15Z"
    - latency: 959.106µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:46:15Z"
    - latency: 1.350229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:45:15Z"
    - latency: 1.141188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:44:15Z"
    - latency: 1.007441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:43:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "60083"
    uid: 194863b7-b02b-4fee-9431-5579d394b51a
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:30:15Z"
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.861619ms
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 8.740544ms
      message: 'load-balancer-api-external: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 3.344299ms
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 9.097989ms
      message: 'load-balancer-api-external: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 4.72549ms
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 7.617938ms
      message: 'load-balancer-api-external: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 4.428421ms
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 8.36002ms
      message: 'load-balancer-api-external: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 3.626313ms
      message: 'load-balancer-api-external: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 8.694695ms
      message: 'load-balancer-api-external: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:50:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "60082"
    uid: f00a2ea7-8cee-4b70-9bcf-55de60b5713d
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:30:15Z"
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.551806ms
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 8.703697ms
      message: 'load-balancer-api-internal: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 5.279595ms
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 9.079142ms
      message: 'load-balancer-api-internal: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 4.779967ms
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 7.339096ms
      message: 'load-balancer-api-internal: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 4.384237ms
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 8.338456ms
      message: 'load-balancer-api-internal: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 3.605642ms
      message: 'load-balancer-api-internal: tcp connection to ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 8.65853ms
      message: 'load-balancer-api-internal: resolved host name ab38924d9f1fd4a3ea69eff4fc9b0d81-847316c8bc5749a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:50:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-network-check-target-ip-10-0-129-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "58336"
    uid: 50d41a3f-2fbb-4d5e-af57-6b022ae1d450
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:31:15Z"
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.564119ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 1.923942ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 1.934682ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 1.968217ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:15Z"
    - latency: 1.869704ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:15Z"
    - latency: 1.896123ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:15Z"
    - latency: 1.889533ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:46:15Z"
    - latency: 1.705461ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:45:15Z"
    - latency: 1.913445ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:44:15Z"
    - latency: 1.550813ms
      message: 'network-check-target-ip-10-0-129-142: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:43:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-network-check-target-ip-10-0-142-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "58337"
    uid: aa1e583c-147d-4f67-a885-4def84a57451
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:31:15Z"
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.477455ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 1.649627ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 1.088112ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 985.711µs
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:15Z"
    - latency: 1.047889ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:15Z"
    - latency: 1.023865ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:15Z"
    - latency: 1.188046ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:46:15Z"
    - latency: 979.984µs
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:45:15Z"
    - latency: 1.005542ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:44:15Z"
    - latency: 1.371834ms
      message: 'network-check-target-ip-10-0-142-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:43:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-network-check-target-ip-10-0-142-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "58335"
    uid: d0620e25-f781-4d7a-aa8a-060fac9b381e
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:31:15Z"
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.654631ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 2.121724ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 2.235437ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 1.812168ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:49:15Z"
    - latency: 1.959778ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:48:15Z"
    - latency: 3.010716ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:47:15Z"
    - latency: 2.361029ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:46:15Z"
    - latency: 2.249645ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:45:15Z"
    - latency: 2.446716ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:44:15Z"
    - latency: 2.09262ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:43:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:24:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-48.ec2.internal
      uid: 66450227-5f88-4975-9b22-c33a7261c347
    resourceVersion: "60081"
    uid: e4e66407-1c8c-4861-a121-a206dd110ebf
  spec:
    sourcePod: network-check-source-6f8b768455-84mpz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:30:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 995.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 1.853008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:54:15Z"
    - latency: 821.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 2.283529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:53:15Z"
    - latency: 893.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 1.459301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:52:15Z"
    - latency: 788.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 1.969015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:51:15Z"
    - latency: 1.077478ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T18:50:15Z"
    - latency: 1.780446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T18:50:15Z"
kind: List
metadata:
  resourceVersion: ""