apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "22134"
    uid: d9bef3bb-be16-45c8-8d54-82e01aaeac18
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:14:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.64µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:57Z"
    - latency: 907.838µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:57Z"
    - latency: 1.078605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:57Z"
    - latency: 909.811µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 965.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 959.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 783.421µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 921.589µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 1.00665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:20:57Z"
    - latency: 1.626048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:19:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "20710"
    uid: af005951-cf4c-445b-8a42-6d04359832d9
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:13:57Z"
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.762188ms
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 8.400246ms
      message: 'load-balancer-api-external: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 4.613933ms
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 9.04932ms
      message: 'load-balancer-api-external: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 4.746781ms
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 8.861998ms
      message: 'load-balancer-api-external: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 5.205399ms
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 9.563147ms
      message: 'load-balancer-api-external: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 5.549498ms
      message: 'load-balancer-api-external: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 8.04881ms
      message: 'load-balancer-api-external: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:21:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "20711"
    uid: 90fcfcdf-d314-4a3d-9834-b50571d9ec42
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:13:57Z"
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.5449ms
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 8.483703ms
      message: 'load-balancer-api-internal: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 4.586211ms
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 9.078624ms
      message: 'load-balancer-api-internal: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 5.27396ms
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 8.928353ms
      message: 'load-balancer-api-internal: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 5.222965ms
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 9.617757ms
      message: 'load-balancer-api-internal: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 5.793734ms
      message: 'load-balancer-api-internal: tcp connection to a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 8.093628ms
      message: 'load-balancer-api-internal: resolved host name a9078c8dff93e4b5dbe90992f723b4ce-adf04142582a792f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:21:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-network-check-target-ip-10-0-132-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "22132"
    uid: 06631d9f-33bf-4c67-a07f-576fdd331383
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:14:57Z"
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.226468ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:57Z"
    - latency: 1.740749ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:57Z"
    - latency: 2.00176ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:57Z"
    - latency: 1.653165ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 1.743918ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 1.945024ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 1.75423ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 1.823195ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 1.85699ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:20:57Z"
    - latency: 1.976808ms
      message: 'network-check-target-ip-10-0-132-145: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:19:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-network-check-target-ip-10-0-136-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "22131"
    uid: f69b2519-e8f4-433d-b37f-1ea96c1edf37
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:14:57Z"
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 828.32µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:57Z"
    - latency: 1.26643ms
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:57Z"
    - latency: 790.344µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:57Z"
    - latency: 766.145µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 768.875µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 961.639µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 921.703µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 805.692µs
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 1.177095ms
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:20:57Z"
    - latency: 1.127945ms
      message: 'network-check-target-ip-10-0-136-131: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:19:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-network-check-target-ip-10-0-136-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "22133"
    uid: 99e2605a-8e38-438f-8ab7-c684f2f81aae
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:14:57Z"
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.224658ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:28:57Z"
    - latency: 2.332355ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:27:57Z"
    - latency: 2.463723ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:26:57Z"
    - latency: 2.024196ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 2.228177ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 2.448772ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 2.315332ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 2.296035ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 2.489437ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:20:57Z"
    - latency: 2.115593ms
      message: 'network-check-target-ip-10-0-136-248: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:19:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-01T18:07:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-131.ec2.internal
      uid: c4c74810-ad28-45a6-8ce8-080839a9d259
    resourceVersion: "20709"
    uid: f49cb245-3d1d-41a7-8f5f-31a68e211ed4
  spec:
    sourcePod: network-check-source-56499946bc-8mcsf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-01T18:13:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.952µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 1.699427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:25:57Z"
    - latency: 847.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 1.671802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:24:57Z"
    - latency: 831.799µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 1.612732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:23:57Z"
    - latency: 770.6µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 2.769839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:22:57Z"
    - latency: 997.707µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-01T18:21:57Z"
    - latency: 1.702541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-01T18:21:57Z"
kind: List
metadata:
  resourceVersion: ""