apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "55622"
    uid: 0575f15e-438d-454e-bc64-3dc832666d99
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:04:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.119804ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 1.202261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 1.562781ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 1.183493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 1.034934ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:28:36Z"
    - latency: 1.116384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:27:36Z"
    - latency: 1.152072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:26:36Z"
    - latency: 2.750152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:25:36Z"
    - latency: 965.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:24:36Z"
    - latency: 1.043166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "56632"
    uid: e5e2249b-e9dc-4467-aeae-7edb6c11a13e
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:03:36Z"
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.674863ms
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 8.761036ms
      message: 'load-balancer-api-external: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 3.705775ms
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 10.285756ms
      message: 'load-balancer-api-external: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 4.914371ms
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 8.841766ms
      message: 'load-balancer-api-external: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 4.339229ms
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 9.997368ms
      message: 'load-balancer-api-external: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 3.514007ms
      message: 'load-balancer-api-external: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 8.220554ms
      message: 'load-balancer-api-external: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "56633"
    uid: a4a6f405-6c25-4cd3-9524-e508a3efac32
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:03:36Z"
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.59308ms
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 8.7976ms
      message: 'load-balancer-api-internal: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 3.675583ms
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 10.330594ms
      message: 'load-balancer-api-internal: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 4.918499ms
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 8.883319ms
      message: 'load-balancer-api-internal: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 4.014193ms
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 10.039256ms
      message: 'load-balancer-api-internal: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 4.907026ms
      message: 'load-balancer-api-internal: tcp connection to a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 8.296089ms
      message: 'load-balancer-api-internal: resolved host name a0533aacda3074cd0b37a929f0eb7e36-c01e105f30be9586.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:29:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-network-check-target-ip-10-0-133-31
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "55619"
    uid: 0a2dd121-071f-475a-9e6a-33f3a60dfdcf
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:04:36Z"
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.535µs
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 1.032611ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 1.946776ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 1.610645ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 876.024µs
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:28:36Z"
    - latency: 917.842µs
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:27:36Z"
    - latency: 1.268131ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:26:36Z"
    - latency: 2.678796ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:25:36Z"
    - latency: 1.558958ms
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:24:36Z"
    - latency: 839.925µs
      message: 'network-check-target-ip-10-0-133-31: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-network-check-target-ip-10-0-134-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "55620"
    uid: cf398cc5-84e0-450c-8359-22b2fc6f1e3e
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:04:36Z"
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.099253ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 2.524921ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 2.652807ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 2.287929ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 2.141083ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:28:36Z"
    - latency: 2.029471ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:27:36Z"
    - latency: 2.552924ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:26:36Z"
    - latency: 3.001789ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:25:36Z"
    - latency: 2.162624ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:24:36Z"
    - latency: 2.361776ms
      message: 'network-check-target-ip-10-0-134-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-network-check-target-ip-10-0-134-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "55621"
    uid: 4d5bc4f5-9f8b-4e14-a4cc-9f31411ab594
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:04:36Z"
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.49145ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 2.247308ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 3.141381ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 2.811731ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 2.772923ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:28:36Z"
    - latency: 2.271776ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:27:36Z"
    - latency: 2.43355ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:26:36Z"
    - latency: 2.919821ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:25:36Z"
    - latency: 2.630322ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:24:36Z"
    - latency: 2.822498ms
      message: 'network-check-target-ip-10-0-134-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:23:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T00:57:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-31-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-31.ec2.internal
      uid: 40578d4e-ea95-4525-9b5b-ca08e054e558
    resourceVersion: "56631"
    uid: eb24e270-5d24-4f27-a7b6-874a1f671093
  spec:
    sourcePod: network-check-source-989f8b8dc-5mtv8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T01:03:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.01634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 2.021304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:33:36Z"
    - latency: 1.402884ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 1.846477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:32:36Z"
    - latency: 820.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 1.879767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:31:36Z"
    - latency: 936.764µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 1.936995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:30:36Z"
    - latency: 1.049807ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T01:29:36Z"
    - latency: 1.715235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T01:29:36Z"
kind: List
metadata:
  resourceVersion: ""