apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "78301"
    uid: 58aa3a03-300d-450d-9d18-dd36980df87b
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:22:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196605ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:11:10Z"
    - latency: 1.117095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:10:10Z"
    - latency: 852.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 1.186625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 1.055159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 1.811161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 1.015204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 1.004391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:04:10Z"
    - latency: 1.391512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:03:10Z"
    - latency: 932.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:02:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "76186"
    uid: 2b37417e-0da1-4d75-aa28-799e3c10922f
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:21:10Z"
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.684052ms
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 6.528608ms
      message: 'load-balancer-api-external: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 8.931374ms
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 8.548195ms
      message: 'load-balancer-api-external: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 5.142424ms
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 8.404247ms
      message: 'load-balancer-api-external: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 5.050672ms
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 7.408496ms
      message: 'load-balancer-api-external: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 4.333406ms
      message: 'load-balancer-api-external: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 8.914613ms
      message: 'load-balancer-api-external: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "76187"
    uid: eba7d3a6-f45c-4f8e-9cb0-a91d5585f061
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:21:10Z"
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.660529ms
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 6.57756ms
      message: 'load-balancer-api-internal: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 8.307287ms
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 8.63615ms
      message: 'load-balancer-api-internal: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 6.063261ms
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 8.333003ms
      message: 'load-balancer-api-internal: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 5.074315ms
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 7.442365ms
      message: 'load-balancer-api-internal: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 5.320694ms
      message: 'load-balancer-api-internal: tcp connection to a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 8.956678ms
      message: 'load-balancer-api-internal: resolved host name a91406ba968ba49af8f05ab457a46f13-9106d61cb8e3b80d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:05:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-135-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "78298"
    uid: a7da2944-7f5d-4c85-972a-b52ac6ddf549
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:22:10Z"
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.188639ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:11:10Z"
    - latency: 2.135243ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:10:10Z"
    - latency: 1.903218ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 2.331271ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 2.252096ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 2.314272ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 2.576355ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 2.359274ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:04:10Z"
    - latency: 2.337212ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:03:10Z"
    - latency: 2.478318ms
      message: 'network-check-target-ip-10-0-135-95: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:02:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-136-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "78300"
    uid: d07a99fe-0ee1-40db-bc90-97dbd7312244
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:22:10Z"
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.067172ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:11:10Z"
    - latency: 2.176619ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:10:10Z"
    - latency: 2.020803ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 2.319014ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 2.165372ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 2.317254ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 2.245252ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 2.230746ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:04:10Z"
    - latency: 2.353358ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:03:10Z"
    - latency: 2.188392ms
      message: 'network-check-target-ip-10-0-136-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:02:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-ip-10-0-138-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "78299"
    uid: 870bf41b-7bae-450e-b25f-9fb2cd290148
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:22:10Z"
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 994.686µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:11:10Z"
    - latency: 1.341071ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:10:10Z"
    - latency: 1.049724ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 1.412311ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 1.013766ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 1.551427ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 919.875µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 1.063496ms
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:04:10Z"
    - latency: 943.97µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:03:10Z"
    - latency: 986.637µs
      message: 'network-check-target-ip-10-0-138-35: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:02:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-04T15:15:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-35.ec2.internal
      uid: 5694e3a2-e935-49fd-aa55-f3b91c036a24
    resourceVersion: "76184"
    uid: 08c979eb-94e3-4cac-82da-7a6939d08240
  spec:
    sourcePod: network-check-source-65bdbbff45-94v75
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-04T15:21:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.376886ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 1.754759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:09:10Z"
    - latency: 933.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 1.681053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:08:10Z"
    - latency: 979.953µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 1.728232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:07:10Z"
    - latency: 1.331406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 1.672998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:06:10Z"
    - latency: 934.84µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-04T16:05:10Z"
    - latency: 1.770012ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-04T16:05:10Z"
kind: List
metadata:
  resourceVersion: ""