apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62918"
    uid: 0af6629f-686e-48bc-a5d2-d39f82a73e09
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:26:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.339435ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 1.011921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 1.016525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 1.225154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 1.553946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 4.080903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:32Z"
    - latency: 1.395518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:32Z"
    - latency: 1.069061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:32Z"
    - latency: 3.348055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:32Z"
    - latency: 1.495331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62919"
    uid: ea3340b2-1066-427a-a2e0-862611bacd4a
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:25:32Z"
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.129201ms
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 7.481806ms
      message: 'load-balancer-api-external: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 6.304904ms
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 7.821725ms
      message: 'load-balancer-api-external: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 4.281157ms
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 7.29138ms
      message: 'load-balancer-api-external: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 3.778368ms
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 6.979996ms
      message: 'load-balancer-api-external: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 4.950141ms
      message: 'load-balancer-api-external: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 6.79739ms
      message: 'load-balancer-api-external: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62920"
    uid: 01a6a2a3-2738-4e8e-adb2-08792437de01
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:25:32Z"
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.413449ms
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 7.394554ms
      message: 'load-balancer-api-internal: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 6.286303ms
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 7.800281ms
      message: 'load-balancer-api-internal: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 4.238271ms
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 7.194853ms
      message: 'load-balancer-api-internal: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 3.40931ms
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 6.938977ms
      message: 'load-balancer-api-internal: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 4.941542ms
      message: 'load-balancer-api-internal: tcp connection to aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 6.727984ms
      message: 'load-balancer-api-internal: resolved host name aca5eb95030eb43aa9ee41ffb953a852-9cf64929b60db46f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-134-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62913"
    uid: b55a0625-7c68-4e0c-b48b-b9c1da823605
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:26:32Z"
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.039792ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 1.752222ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 1.739891ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 962.546µs
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 1.168961ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 4.220679ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:32Z"
    - latency: 1.251367ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:32Z"
    - latency: 1.088139ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:32Z"
    - latency: 6.02431ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:32Z"
    - latency: 1.952717ms
      message: 'network-check-target-ip-10-0-134-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-140-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62915"
    uid: 93646805-e51d-420d-bcd6-28c7c5032acc
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:26:32Z"
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.537994ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 2.421135ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 2.232063ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 2.395395ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 1.983161ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 8.77477ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:32Z"
    - latency: 2.445378ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:32Z"
    - latency: 2.569946ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:32Z"
    - latency: 3.742133ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:32Z"
    - latency: 2.344484ms
      message: 'network-check-target-ip-10-0-140-236: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-ip-10-0-143-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62914"
    uid: 85164d09-c227-4b81-8bd4-b6b98976fd2d
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:26:32Z"
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.087861ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 2.274063ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 2.004407ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 2.210254ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 2.147949ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 3.2027ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:56:32Z"
    - latency: 2.162353ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:55:32Z"
    - latency: 2.270418ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:54:32Z"
    - latency: 2.848234ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:53:32Z"
    - latency: 2.41366ms
      message: 'network-check-target-ip-10-0-143-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:52:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:19:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-72-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-72.ec2.internal
      uid: 948f4905-4156-4474-8671-aa9cecd0f69f
    resourceVersion: "62916"
    uid: 76df2094-707d-4895-912d-6170d43c9288
  spec:
    sourcePod: network-check-source-869dcfcdcd-p77jq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:25:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049224ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 1.847019ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:01:32Z"
    - latency: 951.345µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 2.363837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:00:32Z"
    - latency: 1.214969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 1.932027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:59:32Z"
    - latency: 1.418922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 1.970519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:58:32Z"
    - latency: 903.299µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T19:57:32Z"
    - latency: 2.007084ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T19:57:32Z"
kind: List
metadata:
  resourceVersion: ""