apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "21096"
    uid: bf20797c-5ee3-4837-bba0-55a97317b55f
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:06:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.225972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:13:53Z"
    - latency: 887.614µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:12:53Z"
    - latency: 1.012678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 930.83µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 971.898µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 1.265993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 1.25154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 1.256047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:06:53Z"
    - latency: 1.119945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:05:53Z"
    - latency: 976.11µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:04:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "20196"
    uid: deb07066-08f5-46cd-8981-b18d55d8ee2e
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:05:53Z"
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.977009ms
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 8.757319ms
      message: 'load-balancer-api-external: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 5.754276ms
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 8.723918ms
      message: 'load-balancer-api-external: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 4.629255ms
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 7.577044ms
      message: 'load-balancer-api-external: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 4.598908ms
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 9.726066ms
      message: 'load-balancer-api-external: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 5.245621ms
      message: 'load-balancer-api-external: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 8.4938ms
      message: 'load-balancer-api-external: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:07:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "20195"
    uid: fbab2080-d570-4eba-a34a-6d544b9d34be
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:05:53Z"
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.297773ms
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 8.689537ms
      message: 'load-balancer-api-internal: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 5.796263ms
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 8.650059ms
      message: 'load-balancer-api-internal: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 4.627829ms
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 7.535679ms
      message: 'load-balancer-api-internal: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 4.425351ms
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 9.666208ms
      message: 'load-balancer-api-internal: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 5.393602ms
      message: 'load-balancer-api-internal: tcp connection to a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 8.543244ms
      message: 'load-balancer-api-internal: resolved host name a54fe38267e2449bea15b25e873c31d1-7a8857a9cf303b06.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:07:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-129-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "21094"
    uid: 589f075a-e319-4be2-b04e-ecf4354182b5
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:06:53Z"
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.053948ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:13:53Z"
    - latency: 2.324179ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:12:53Z"
    - latency: 1.924015ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 2.216357ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 2.06634ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 2.120874ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 2.440069ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 2.258917ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:06:53Z"
    - latency: 2.045521ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:05:53Z"
    - latency: 1.953327ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:04:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-131-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "21093"
    uid: 2ef60350-83bd-4ec5-bbcf-f5b1fa15d966
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:06:53Z"
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.114725ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:13:53Z"
    - latency: 1.065579ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:12:53Z"
    - latency: 916.917µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 1.214002ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 869.161µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 914.45µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 947.042µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 1.127802ms
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:06:53Z"
    - latency: 814.933µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:05:53Z"
    - latency: 969.097µs
      message: 'network-check-target-ip-10-0-131-227: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:04:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-ip-10-0-143-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "21095"
    uid: 8ebe3923-1e75-4fc2-b33c-2eb26a1af60a
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:06:53Z"
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.032831ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:13:53Z"
    - latency: 1.762282ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:12:53Z"
    - latency: 2.251917ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 2.080118ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 2.171941ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 1.876525ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 2.172041ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 1.918009ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:06:53Z"
    - latency: 1.836533ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:05:53Z"
    - latency: 1.933896ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:04:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T00:59:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-227.us-east-2.compute.internal
      uid: 3f33e5f3-e6e7-4130-a8d0-a335a4343b80
    resourceVersion: "20194"
    uid: f60a44fd-6273-4a45-9835-4a4fdfee5a03
  spec:
    sourcePod: network-check-source-6f78d59f99-7jtmg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T01:05:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.143702ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 2.214365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:11:53Z"
    - latency: 1.051681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 2.021193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:10:53Z"
    - latency: 1.026654ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 1.908336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:09:53Z"
    - latency: 787.987µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 1.752294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:08:53Z"
    - latency: 1.508625ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T01:07:53Z"
    - latency: 1.855425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T01:07:53Z"
kind: List
metadata:
  resourceVersion: ""