apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41159"
    uid: 0b52e9e8-3226-44e2-8ca4-25588c40592f
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.22255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 1.55331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 1.196967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 976.586µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 1.084736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:25:29Z"
    - latency: 1.898572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:24:29Z"
    - latency: 1.328387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:23:29Z"
    - latency: 1.331638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:22:29Z"
    - latency: 1.191027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:21:29Z"
    - latency: 1.229032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:20:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41790"
    uid: e279da76-2301-4e3b-8bbc-f38ba4984ee4
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.37873ms
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 10.552562ms
      message: 'load-balancer-api-external: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 6.825281ms
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 10.239278ms
      message: 'load-balancer-api-external: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 4.622248ms
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 7.343005ms
      message: 'load-balancer-api-external: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 5.411625ms
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 13.44445ms
      message: 'load-balancer-api-external: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 5.079647ms
      message: 'load-balancer-api-external: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 10.901519ms
      message: 'load-balancer-api-external: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:26:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41789"
    uid: e6d16144-f326-4e74-bd20-f872753a3cc1
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.342621ms
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 10.512166ms
      message: 'load-balancer-api-internal: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 6.161ms
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 10.197572ms
      message: 'load-balancer-api-internal: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 4.646923ms
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 7.205609ms
      message: 'load-balancer-api-internal: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 6.988686ms
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 13.362088ms
      message: 'load-balancer-api-internal: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 4.886689ms
      message: 'load-balancer-api-internal: tcp connection to a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 10.868233ms
      message: 'load-balancer-api-internal: resolved host name a8ee48e8966594053bd8937f0e865000-71e4bbb1f59d9b56.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:26:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-134-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41158"
    uid: 5fc943f7-1a7d-446a-8823-6f3628222736
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.920016ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 2.35621ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 2.678637ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 981.208µs
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 885.011µs
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:25:29Z"
    - latency: 1.137015ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:24:29Z"
    - latency: 1.012347ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:23:29Z"
    - latency: 997.115µs
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:22:29Z"
    - latency: 1.18078ms
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:21:29Z"
    - latency: 824.818µs
      message: 'network-check-target-ip-10-0-134-156: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:20:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-135-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41156"
    uid: 376c55c0-807c-43d4-bc34-f652f3d4101e
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.472048ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 2.985084ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 3.355744ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 2.357323ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 2.107885ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:25:29Z"
    - latency: 2.171992ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:24:29Z"
    - latency: 2.270537ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:23:29Z"
    - latency: 2.494396ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:22:29Z"
    - latency: 2.216933ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:21:29Z"
    - latency: 2.45319ms
      message: 'network-check-target-ip-10-0-135-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:20:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-network-check-target-ip-10-0-139-76
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41157"
    uid: e789f8a1-64ac-4fd0-884b-790d7407061e
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:01:29Z"
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.413446ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 2.61357ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 3.157514ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 1.808032ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 2.18877ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:25:29Z"
    - latency: 2.093588ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:24:29Z"
    - latency: 2.292663ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:23:29Z"
    - latency: 1.775012ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:22:29Z"
    - latency: 1.853505ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:21:29Z"
    - latency: 2.144279ms
      message: 'network-check-target-ip-10-0-139-76: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:20:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T16:54:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-156-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-156.ec2.internal
      uid: 61fef169-2541-4717-a989-e15dd9d4c365
    resourceVersion: "41788"
    uid: 2cda4095-9c48-4669-970c-8e267e406634
  spec:
    sourcePod: network-check-source-7d88cb55d8-tv5bc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T17:00:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 1.94925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:30:29Z"
    - latency: 1.113222ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 2.116004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:29:29Z"
    - latency: 1.173646ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 2.458939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:28:29Z"
    - latency: 1.453195ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 3.976818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:27:29Z"
    - latency: 840.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T17:26:29Z"
    - latency: 3.427504ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T17:26:29Z"
kind: List
metadata:
  resourceVersion: ""