apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "28373"
    uid: 87fd38a9-5141-4026-a38a-638584ee8c71
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:38:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.142µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:45:45Z"
    - latency: 995.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:44:45Z"
    - latency: 1.100884ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 1.081335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 1.064134ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 854.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 972.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 958.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:38:45Z"
    - latency: 915.591µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:37:45Z"
    - latency: 1.069982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:36:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "26677"
    uid: dfb92fa5-5ea5-4bac-8d1c-73b44fb862b6
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:37:45Z"
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.372174ms
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 7.333033ms
      message: 'load-balancer-api-external: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 5.526443ms
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 7.848313ms
      message: 'load-balancer-api-external: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 3.870453ms
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 6.809678ms
      message: 'load-balancer-api-external: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 5.22936ms
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 10.350937ms
      message: 'load-balancer-api-external: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 4.924302ms
      message: 'load-balancer-api-external: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 6.751881ms
      message: 'load-balancer-api-external: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:39:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "26678"
    uid: 6bd8560d-e569-4c57-9812-cf1f7c02a818
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:37:45Z"
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.365405ms
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 7.364798ms
      message: 'load-balancer-api-internal: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 5.536227ms
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 7.826873ms
      message: 'load-balancer-api-internal: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 4.500296ms
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 6.891628ms
      message: 'load-balancer-api-internal: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 5.20657ms
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 10.431506ms
      message: 'load-balancer-api-internal: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 11.673934ms
      message: 'load-balancer-api-internal: tcp connection to a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 6.845772ms
      message: 'load-balancer-api-internal: resolved host name a7589bd50bca449d6ad784d98265947d-6394fd5960760669.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:39:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-network-check-target-ip-10-0-132-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "28371"
    uid: fa55968e-0f7d-4884-850a-a9960269d6be
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:38:45Z"
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.359089ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:45:45Z"
    - latency: 2.099547ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:44:45Z"
    - latency: 2.22196ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 2.085775ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 1.818549ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 2.411953ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 2.16496ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 2.147553ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:38:45Z"
    - latency: 1.943273ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:37:45Z"
    - latency: 2.234032ms
      message: 'network-check-target-ip-10-0-132-239: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:36:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-network-check-target-ip-10-0-139-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "28370"
    uid: 0da16ee1-bbb0-413a-a595-9328e3689747
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:38:45Z"
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.51895ms
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:45:45Z"
    - latency: 1.153948ms
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:44:45Z"
    - latency: 818.191µs
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 1.678421ms
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 772.55µs
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 1.054032ms
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 760.612µs
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 843.916µs
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:38:45Z"
    - latency: 1.245269ms
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:37:45Z"
    - latency: 864.089µs
      message: 'network-check-target-ip-10-0-139-121: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:36:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-network-check-target-ip-10-0-141-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "28372"
    uid: e1dc9888-ee08-46a2-834b-04109de2a684
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:38:45Z"
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.317057ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:45:45Z"
    - latency: 2.122474ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:44:45Z"
    - latency: 2.060923ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 2.050446ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 1.70581ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 1.803194ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 2.011525ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 1.829929ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:38:45Z"
    - latency: 1.952054ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:37:45Z"
    - latency: 2.232887ms
      message: 'network-check-target-ip-10-0-141-209: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:36:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-11T12:31:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-121-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-121.ec2.internal
      uid: 70baf81e-2d49-4b18-ac82-77fbcfc058eb
    resourceVersion: "26676"
    uid: 72e3ddaa-25e4-45ec-859c-c671d8e3fb70
  spec:
    sourcePod: network-check-source-dbd9cf844-xx5fx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-11T12:37:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013133ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 1.916259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:43:45Z"
    - latency: 1.058722ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 1.520295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:42:45Z"
    - latency: 958.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 1.671635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:41:45Z"
    - latency: 948.186µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 1.617926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:40:45Z"
    - latency: 1.154353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-11T12:39:45Z"
    - latency: 1.771161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-11T12:39:45Z"
kind: List
metadata:
  resourceVersion: ""