apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "19430"
    uid: c8b46a85-e43f-44f4-8c4c-0304a8481168
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:41:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.069µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 1.048953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 982.68µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:59Z"
    - latency: 1.091368ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:59Z"
    - latency: 911.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:59Z"
    - latency: 902.673µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:50:59Z"
    - latency: 1.056128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:49:59Z"
    - latency: 1.073219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:48:59Z"
    - latency: 1.143092ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:47:59Z"
    - latency: 777.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:46:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "20698"
    uid: 427ba794-d306-413a-af21-1299d326a3dc
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:40:59Z"
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.933379ms
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 8.044175ms
      message: 'load-balancer-api-external: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 4.913387ms
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 8.285737ms
      message: 'load-balancer-api-external: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 5.907899ms
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 8.038881ms
      message: 'load-balancer-api-external: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 4.951358ms
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 8.780964ms
      message: 'load-balancer-api-external: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 4.075368ms
      message: 'load-balancer-api-external: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 7.911031ms
      message: 'load-balancer-api-external: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "20697"
    uid: 6820a76d-a47c-4772-88e2-e4bb5a626eea
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:40:59Z"
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.952898ms
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 7.830832ms
      message: 'load-balancer-api-internal: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 4.872361ms
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 8.348131ms
      message: 'load-balancer-api-internal: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 5.846645ms
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 8.069645ms
      message: 'load-balancer-api-internal: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 7.241021ms
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 8.852636ms
      message: 'load-balancer-api-internal: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 4.129006ms
      message: 'load-balancer-api-internal: tcp connection to af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 7.946941ms
      message: 'load-balancer-api-internal: resolved host name af004eedeaeb14224b08161008ec0cf4-c52da112c32a5c2e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-131-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "19427"
    uid: 229abf18-0bbb-4b97-9f65-910650ce77f7
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:41:59Z"
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 777.447µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 852.537µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 855.365µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:59Z"
    - latency: 981.251µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:59Z"
    - latency: 696.172µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:59Z"
    - latency: 876.841µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:50:59Z"
    - latency: 1.205375ms
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:49:59Z"
    - latency: 941.366µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:48:59Z"
    - latency: 850.635µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:47:59Z"
    - latency: 831.605µs
      message: 'network-check-target-ip-10-0-131-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:46:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-137-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "19428"
    uid: a3508b69-7350-479f-a26a-b606214951c4
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:41:59Z"
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.871351ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 1.906426ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 1.72159ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:59Z"
    - latency: 1.866656ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:59Z"
    - latency: 1.891571ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:59Z"
    - latency: 1.874283ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:50:59Z"
    - latency: 2.033169ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:49:59Z"
    - latency: 2.074726ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:48:59Z"
    - latency: 1.952944ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:47:59Z"
    - latency: 1.744814ms
      message: 'network-check-target-ip-10-0-137-190: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:46:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-network-check-target-ip-10-0-138-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "19429"
    uid: 6e49798d-bdc3-4d63-a46e-e1f276125cd8
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:41:59Z"
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.029724ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 2.043469ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 1.902352ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:53:59Z"
    - latency: 2.054057ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:52:59Z"
    - latency: 2.018357ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:51:59Z"
    - latency: 1.97099ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:50:59Z"
    - latency: 2.03689ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:49:59Z"
    - latency: 2.273094ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:48:59Z"
    - latency: 2.330498ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:47:59Z"
    - latency: 1.959537ms
      message: 'network-check-target-ip-10-0-138-109: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:46:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T17:34:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-83.ec2.internal
      uid: 88c87f40-39ec-43c8-ab42-2c19eb30da56
    resourceVersion: "20696"
    uid: 9ed8c7a9-4e8a-42a5-8d52-f5db064b1279
  spec:
    sourcePod: network-check-source-869dcfcdcd-5zxhn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T17:40:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 836.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 2.249291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:58:59Z"
    - latency: 812.35µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 1.598623ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:57:59Z"
    - latency: 869.488µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 1.619134ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:56:59Z"
    - latency: 785.547µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 2.214545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:55:59Z"
    - latency: 1.235412ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T17:54:59Z"
    - latency: 1.684817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T17:54:59Z"
kind: List
metadata:
  resourceVersion: ""