apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "103098"
    uid: c41823ed-5273-4619-bb9a-1530096a493f
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:24:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 1.507278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 991.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 1.132556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:24:09Z"
    - latency: 1.815771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:23:09Z"
    - latency: 1.337954ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:22:09Z"
    - latency: 962.235µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:21:09Z"
    - latency: 1.117002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:20:09Z"
    - latency: 865.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:19:09Z"
    - latency: 1.300655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:18:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "104205"
    uid: 0c3a08e9-c1f6-49a2-8696-965e14ebf909
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:23:10Z"
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.942097ms
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 8.139027ms
      message: 'load-balancer-api-external: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 49.671559ms
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 8.106903ms
      message: 'load-balancer-api-external: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 51.004758ms
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 8.458688ms
      message: 'load-balancer-api-external: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 54.566319ms
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 8.0149ms
      message: 'load-balancer-api-external: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 52.130167ms
      message: 'load-balancer-api-external: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 8.011546ms
      message: 'load-balancer-api-external: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "104204"
    uid: c7c7c72a-bdc0-47b0-811c-e7c4b26875dc
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:23:10Z"
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 49.777195ms
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 8.024278ms
      message: 'load-balancer-api-internal: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 53.301702ms
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 8.023304ms
      message: 'load-balancer-api-internal: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 50.987282ms
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 8.375648ms
      message: 'load-balancer-api-internal: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 51.898122ms
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 8.050704ms
      message: 'load-balancer-api-internal: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 50.360042ms
      message: 'load-balancer-api-internal: tcp connection to aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 7.976888ms
      message: 'load-balancer-api-internal: resolved host name aa9979ce62f3e4f9a86916a6635549a1-220db26bc9a348ee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:25:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-network-check-target-ip-10-0-129-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "103094"
    uid: 883f6d4a-6e26-43e3-8414-56b53e2d5be8
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:24:09Z"
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.371575ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 2.770746ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 2.556043ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 2.367705ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:24:09Z"
    - latency: 2.431993ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:23:09Z"
    - latency: 2.76706ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:22:09Z"
    - latency: 2.269695ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:21:09Z"
    - latency: 2.593535ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:20:09Z"
    - latency: 2.218548ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:19:09Z"
    - latency: 2.460618ms
      message: 'network-check-target-ip-10-0-129-83: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:18:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-network-check-target-ip-10-0-132-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "103093"
    uid: 682426eb-9d91-4220-8bfd-58281f7a58d4
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:24:09Z"
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.398321ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 1.668927ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 961.471µs
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 1.81686ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:24:09Z"
    - latency: 889.584µs
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:23:09Z"
    - latency: 1.954709ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:22:09Z"
    - latency: 1.342674ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:21:09Z"
    - latency: 1.892252ms
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:20:09Z"
    - latency: 985.787µs
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:19:09Z"
    - latency: 942.439µs
      message: 'network-check-target-ip-10-0-132-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:18:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-network-check-target-ip-10-0-142-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "103096"
    uid: 6bf7ab95-0187-4a35-bbef-c3697f69aa85
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:24:09Z"
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.394834ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 2.701211ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 2.657621ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 2.204414ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:24:09Z"
    - latency: 2.685415ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:23:09Z"
    - latency: 2.054323ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:22:09Z"
    - latency: 1.96766ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:21:09Z"
    - latency: 2.397657ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:20:09Z"
    - latency: 2.369745ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:19:09Z"
    - latency: 2.298845ms
      message: 'network-check-target-ip-10-0-142-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:18:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:17:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-23.us-west-2.compute.internal
      uid: a71488f2-67bb-49ca-8281-04d6b7db93a4
    resourceVersion: "104202"
    uid: 12ce0a4c-8265-4058-bd78-51a7a2feaa46
  spec:
    sourcePod: network-check-source-6f78d59f99-gbtvd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:23:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.366099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 2.254466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:29:09Z"
    - latency: 1.195917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 1.572805ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:28:09Z"
    - latency: 1.020068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 2.435601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:27:09Z"
    - latency: 1.134834ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 2.038703ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:26:09Z"
    - latency: 1.482987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:25:09Z"
    - latency: 1.884546ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:25:09Z"
kind: List
metadata:
  resourceVersion: ""