apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "80772"
    uid: 75e4936c-637b-45d3-be83-2dee47c0bb4c
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.226328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 922.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:43:45Z"
    - latency: 969.777µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:42:45Z"
    - latency: 1.12783ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:41:45Z"
    - latency: 1.056464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:40:45Z"
    - latency: 1.926796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:39:45Z"
    - latency: 1.04745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:45Z"
    - latency: 1.104488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:45Z"
    - latency: 1.083855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:45Z"
    - latency: 949.859µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "84578"
    uid: e24d843e-05d2-44f2-94fc-bf22d57b68cf
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:54:45Z"
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.419326ms
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 8.504743ms
      message: 'load-balancer-api-external: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 4.893535ms
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 7.788779ms
      message: 'load-balancer-api-external: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 4.921704ms
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 8.242404ms
      message: 'load-balancer-api-external: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 4.468935ms
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 8.320052ms
      message: 'load-balancer-api-external: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 4.867721ms
      message: 'load-balancer-api-external: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 8.846224ms
      message: 'load-balancer-api-external: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "84579"
    uid: 2a1cd9a7-43f9-4be1-b653-bb03d8808c3f
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:54:45Z"
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.609729ms
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 8.462847ms
      message: 'load-balancer-api-internal: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 4.943224ms
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 7.768592ms
      message: 'load-balancer-api-internal: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 4.487811ms
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 8.220836ms
      message: 'load-balancer-api-internal: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 3.060657ms
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 8.292301ms
      message: 'load-balancer-api-internal: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 4.234766ms
      message: 'load-balancer-api-internal: tcp connection to acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 8.839391ms
      message: 'load-balancer-api-internal: resolved host name acf058585c85c4dc08dca9d7214ffce2-dbf6f594e8ed523c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-network-check-target-ip-10-0-130-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "80769"
    uid: ff977817-e1a0-4ff5-8abd-f6e7c37470e2
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:45Z"
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193458ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 1.043002ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:43:45Z"
    - latency: 1.618771ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:42:45Z"
    - latency: 1.065446ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:41:45Z"
    - latency: 1.501406ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:40:45Z"
    - latency: 1.59799ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:39:45Z"
    - latency: 1.266077ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:45Z"
    - latency: 1.058271ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:45Z"
    - latency: 1.046172ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:45Z"
    - latency: 1.497903ms
      message: 'network-check-target-ip-10-0-130-148: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-network-check-target-ip-10-0-131-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "80770"
    uid: 36bcdc7e-0793-47cd-bed8-ba9c57547762
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:45Z"
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.122956ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 1.96827ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:43:45Z"
    - latency: 1.993579ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:42:45Z"
    - latency: 2.075114ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:41:45Z"
    - latency: 2.045092ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:40:45Z"
    - latency: 2.169664ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:39:45Z"
    - latency: 2.118743ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:45Z"
    - latency: 1.896943ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:45Z"
    - latency: 1.854422ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:45Z"
    - latency: 2.261027ms
      message: 'network-check-target-ip-10-0-131-136: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-network-check-target-ip-10-0-140-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "80771"
    uid: e23f1702-805e-4849-aa9d-57786f680df5
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:55:45Z"
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.338912ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 2.258622ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:43:45Z"
    - latency: 2.342318ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:42:45Z"
    - latency: 2.334126ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:41:45Z"
    - latency: 2.400302ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:40:45Z"
    - latency: 2.217344ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:39:45Z"
    - latency: 2.543719ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:38:45Z"
    - latency: 2.517504ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:37:45Z"
    - latency: 2.14696ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:36:45Z"
    - latency: 2.652295ms
      message: 'network-check-target-ip-10-0-140-3: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:35:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T23:48:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-148.ec2.internal
      uid: a9f972ff-6484-4d89-90e9-0272f905d42a
    resourceVersion: "84576"
    uid: 42559b26-cfcd-4578-a137-1a94b7fa837d
  spec:
    sourcePod: network-check-source-65bdbbff45-2lwvf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T23:54:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.438µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 1.72649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:48:45Z"
    - latency: 941.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 1.611696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:47:45Z"
    - latency: 834.01µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 1.71927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:46:45Z"
    - latency: 1.08992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 1.798963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:45:45Z"
    - latency: 1.530925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-01T00:44:45Z"
    - latency: 1.801594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-01T00:44:45Z"
kind: List
metadata:
  resourceVersion: ""