apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38866"
    uid: 5b5288d6-4b08-4b7d-a2c8-bce56b6cbdfd
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:09:16Z"
    - latency: 837.536µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 746.425µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 954.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 1.09899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 952.068µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 1.209453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:16Z"
    - latency: 979.416µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:16Z"
    - latency: 745.555µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:16Z"
    - latency: 974.348µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38278"
    uid: 30b70385-dfb1-4b94-95f9-b2e33bb534e4
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:16Z"
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.209928ms
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 7.64676ms
      message: 'load-balancer-api-external: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 4.375649ms
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 8.227078ms
      message: 'load-balancer-api-external: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 4.79066ms
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 6.957046ms
      message: 'load-balancer-api-external: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 4.682877ms
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 7.893752ms
      message: 'load-balancer-api-external: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 3.622481ms
      message: 'load-balancer-api-external: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 7.942201ms
      message: 'load-balancer-api-external: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:04:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38279"
    uid: c8684ac4-827f-4a7b-ab3f-82a3badea7ae
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:16Z"
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.160352ms
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 7.567987ms
      message: 'load-balancer-api-internal: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 4.553254ms
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 8.269893ms
      message: 'load-balancer-api-internal: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 4.463502ms
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 6.881077ms
      message: 'load-balancer-api-internal: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 4.646929ms
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 8.021123ms
      message: 'load-balancer-api-internal: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 4.051285ms
      message: 'load-balancer-api-internal: tcp connection to a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 7.848582ms
      message: 'load-balancer-api-internal: resolved host name a263150e67f974110910b1446bd3d68e-76456f09a57a10aa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:04:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-139-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38865"
    uid: 0fb09b34-306a-449a-b890-036b3eadae9d
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:16Z"
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.651627ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:09:16Z"
    - latency: 2.182805ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 2.299346ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 2.488174ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 2.332389ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 2.568336ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 2.364315ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:16Z"
    - latency: 2.461654ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:16Z"
    - latency: 2.157707ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:16Z"
    - latency: 2.683846ms
      message: 'network-check-target-ip-10-0-139-25: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-142-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38863"
    uid: 08020dfe-5567-42d4-8635-3e74324ab006
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:16Z"
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079315ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:09:16Z"
    - latency: 1.873515ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 1.999725ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 2.124425ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 1.949362ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 1.95923ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 1.853931ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:16Z"
    - latency: 1.980841ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:16Z"
    - latency: 2.109181ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:16Z"
    - latency: 2.115053ms
      message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-ip-10-0-143-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38864"
    uid: 4c402c57-6aef-4941-89a2-0e4c0e4b8180
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:27:16Z"
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.658µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:09:16Z"
    - latency: 1.228163ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 667.25µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 1.323721ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 1.197821ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 854.72µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 1.406269ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:03:16Z"
    - latency: 1.307091ms
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:02:16Z"
    - latency: 838.009µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:01:16Z"
    - latency: 880.644µs
      message: 'network-check-target-ip-10-0-143-197: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:00:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T16:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-197.ec2.internal
      uid: 8a063af7-ede5-4006-b3d7-f712acafc531
    resourceVersion: "38277"
    uid: 1148379d-775b-467b-857d-af47fb724e2c
  spec:
    sourcePod: network-check-source-6f8b768455-hwvmz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T16:26:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087115ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 1.97422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:08:16Z"
    - latency: 1.09685ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 1.903302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:07:16Z"
    - latency: 984.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 1.83839ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:06:16Z"
    - latency: 1.028101ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 1.786378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:05:16Z"
    - latency: 954.527µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T17:04:16Z"
    - latency: 1.802338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T17:04:16Z"
kind: List
metadata:
  resourceVersion: ""