apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "58158"
    uid: b1c1e640-2d6a-4883-8fae-96f09ad8f522
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:06:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.744µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 937.233µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 1.218618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 1.315544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:24:50Z"
    - latency: 1.267105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:50Z"
    - latency: 837.06µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:50Z"
    - latency: 1.777614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:50Z"
    - latency: 1.033099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:50Z"
    - latency: 920.709µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:50Z"
    - latency: 1.080178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "59849"
    uid: 5ea14e86-1905-4a8c-9ee8-7fb6b2f8c01e
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:05:50Z"
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.003308ms
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 7.788792ms
      message: 'load-balancer-api-external: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 4.652295ms
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 9.002598ms
      message: 'load-balancer-api-external: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 5.145142ms
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 8.831584ms
      message: 'load-balancer-api-external: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 4.025974ms
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 8.829008ms
      message: 'load-balancer-api-external: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 4.938274ms
      message: 'load-balancer-api-external: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 8.231452ms
      message: 'load-balancer-api-external: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:25:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "59850"
    uid: 584c4332-4545-4121-aec7-551ab2cebf5e
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:05:50Z"
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.655936ms
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 7.89202ms
      message: 'load-balancer-api-internal: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 4.618682ms
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 9.078445ms
      message: 'load-balancer-api-internal: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 4.608833ms
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 8.785005ms
      message: 'load-balancer-api-internal: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 5.135977ms
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 8.893744ms
      message: 'load-balancer-api-internal: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 4.78746ms
      message: 'load-balancer-api-internal: tcp connection to a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 8.416478ms
      message: 'load-balancer-api-internal: resolved host name a3748d53fc2ff47d7985c67a407a918d-0c05428cde22bd5b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:25:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-network-check-target-ip-10-0-133-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "58155"
    uid: 4c508dd2-2e75-4b66-acec-33439b84e6a2
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:06:50Z"
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.998µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 879.754µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 839.391µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 1.544761ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:24:50Z"
    - latency: 944.128µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:50Z"
    - latency: 913.47µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:50Z"
    - latency: 1.161323ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:50Z"
    - latency: 990.483µs
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:50Z"
    - latency: 1.287731ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:50Z"
    - latency: 1.457343ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-network-check-target-ip-10-0-142-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "58157"
    uid: 29d0cf6c-f005-439b-aad5-36affa31857c
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:06:50Z"
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.192024ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 2.056618ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 2.030725ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 2.424047ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:24:50Z"
    - latency: 2.207365ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:50Z"
    - latency: 2.552548ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:50Z"
    - latency: 2.240612ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:50Z"
    - latency: 2.511832ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:50Z"
    - latency: 2.427576ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:50Z"
    - latency: 2.333882ms
      message: 'network-check-target-ip-10-0-142-110: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-network-check-target-ip-10-0-143-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "58156"
    uid: d2b363a2-8dfb-4950-ac9c-deb56e457d89
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:06:50Z"
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.870512ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 1.950219ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 1.817322ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 1.738824ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:24:50Z"
    - latency: 2.345309ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:50Z"
    - latency: 2.371203ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:50Z"
    - latency: 2.416613ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:50Z"
    - latency: 1.957459ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:50Z"
    - latency: 2.086707ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:50Z"
    - latency: 1.939039ms
      message: 'network-check-target-ip-10-0-143-6: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:59:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-79-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-79.ec2.internal
      uid: c6c3b29b-136c-4e05-b7f9-a01c500680ce
    resourceVersion: "59848"
    uid: 1704435a-a4cf-4b71-b64b-76ec571d7c8b
  spec:
    sourcePod: network-check-source-6f8b768455-8wp9p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:05:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 1.762461ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:29:50Z"
    - latency: 837.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 1.934526ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:28:50Z"
    - latency: 828.501µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 2.096854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:27:50Z"
    - latency: 1.462689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 1.764984ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:26:50Z"
    - latency: 699.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:25:50Z"
    - latency: 1.838482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:25:50Z"
kind: List
metadata:
  resourceVersion: ""