apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62849"
    uid: ac5d9cb0-ec3e-48d6-8f57-01dc12e41faa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T16:00:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.058153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 923.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 1.536569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 954.698µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 1.120011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 1.013331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:30:04Z"
    - latency: 1.138629ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:29:04Z"
    - latency: 973.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:28:04Z"
    - latency: 1.026484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:27:04Z"
    - latency: 854.658µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62851"
    uid: f739ff09-ba73-4127-aaef-8ab01eeb792f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:59:04Z"
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.451019ms
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 10.272288ms
      message: 'load-balancer-api-external: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 7.847443ms
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 9.40968ms
      message: 'load-balancer-api-external: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 4.185227ms
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 9.70206ms
      message: 'load-balancer-api-external: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 3.915936ms
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 9.812292ms
      message: 'load-balancer-api-external: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 3.459768ms
      message: 'load-balancer-api-external: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 9.43183ms
      message: 'load-balancer-api-external: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:31:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62850"
    uid: 8fdea9a5-88bf-4d62-ab19-40946763453b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:59:04Z"
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.258621ms
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 10.233775ms
      message: 'load-balancer-api-internal: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 5.931519ms
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 9.369677ms
      message: 'load-balancer-api-internal: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 4.217038ms
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 9.667591ms
      message: 'load-balancer-api-internal: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 3.454131ms
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 9.77293ms
      message: 'load-balancer-api-internal: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 3.466077ms
      message: 'load-balancer-api-internal: tcp connection to a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 9.230496ms
      message: 'load-balancer-api-internal: resolved host name a0ff583bc9e74491a8a8d07d928f44f7-821f6973b1a91747.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:31:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-network-check-target-ip-10-0-128-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62847"
    uid: 5b846280-8918-4b85-b927-bab70af16b26
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T16:00:04Z"
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.307652ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 1.956388ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 2.274996ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 2.233218ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 2.290791ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 2.089864ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:30:04Z"
    - latency: 2.328197ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:29:04Z"
    - latency: 2.258207ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:28:04Z"
    - latency: 2.202984ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:27:04Z"
    - latency: 2.370575ms
      message: 'network-check-target-ip-10-0-128-121: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-network-check-target-ip-10-0-137-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62845"
    uid: df525276-750b-41cb-b271-17cc076e0636
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T16:00:04Z"
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.859µs
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 1.009056ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 879.896µs
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 1.166122ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 1.519097ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 1.001575ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:30:04Z"
    - latency: 906.952µs
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:29:04Z"
    - latency: 1.16188ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:28:04Z"
    - latency: 970.142µs
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:27:04Z"
    - latency: 861.529µs
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-network-check-target-ip-10-0-140-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62846"
    uid: b68cb64f-de27-4849-89d2-f04d7e2845e2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T16:00:04Z"
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.180793ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 2.264115ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 1.952854ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 2.098622ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 2.252623ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 2.099842ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:30:04Z"
    - latency: 2.638525ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:29:04Z"
    - latency: 2.07127ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:28:04Z"
    - latency: 2.367581ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:27:04Z"
    - latency: 2.406872ms
      message: 'network-check-target-ip-10-0-140-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:53:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-185-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-185.ec2.internal
      uid: f38c7760-be32-4273-80f3-49220ea2d012
    resourceVersion: "62848"
    uid: d772902d-74ab-4b62-9b51-66ae0533bb75
  spec:
    sourcePod: network-check-source-7bc5b6bf85-g8p67
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:59:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.068487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 1.909777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:35:04Z"
    - latency: 1.007618ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 1.901542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:34:04Z"
    - latency: 1.095071ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 1.940042ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:33:04Z"
    - latency: 961.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 2.311743ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:32:04Z"
    - latency: 926.479µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T16:31:04Z"
    - latency: 1.95196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T16:31:04Z"
kind: List
metadata:
  resourceVersion: ""