apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "67820"
    uid: adef2f49-73f3-455b-a90f-e25ae9cb0b5d
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:28:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.337853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 1.037145ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 901.126µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 1.005277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 932.327µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:37Z"
    - latency: 1.556601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:37Z"
    - latency: 1.01198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:37Z"
    - latency: 1.456655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:37Z"
    - latency: 1.091943ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:37Z"
    - latency: 923.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "68669"
    uid: bf57bef7-e284-4076-b8a8-d5a1ba94ddc4
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:37Z"
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.739438ms
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 8.77311ms
      message: 'load-balancer-api-external: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 3.977078ms
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 9.277433ms
      message: 'load-balancer-api-external: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 5.069631ms
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 8.703078ms
      message: 'load-balancer-api-external: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 4.332659ms
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 9.909523ms
      message: 'load-balancer-api-external: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 4.304341ms
      message: 'load-balancer-api-external: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 9.320634ms
      message: 'load-balancer-api-external: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "68668"
    uid: e2bca4dd-b447-419d-96a6-d91356aec551
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:37Z"
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.734657ms
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 8.693081ms
      message: 'load-balancer-api-internal: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 3.941136ms
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 9.313588ms
      message: 'load-balancer-api-internal: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 5.070302ms
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 8.733877ms
      message: 'load-balancer-api-internal: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 3.947369ms
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 9.964864ms
      message: 'load-balancer-api-internal: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 4.32208ms
      message: 'load-balancer-api-internal: tcp connection to adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 9.353855ms
      message: 'load-balancer-api-internal: resolved host name adb79aaba5b2c41c491c69fcdd8f1264-fd0831789717dfdf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-network-check-target-ip-10-0-139-186
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "67817"
    uid: 40705cf4-5461-4035-b29e-e0c448a81da4
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:28:37Z"
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.607402ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 989.253µs
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 1.5943ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 1.119184ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 1.487588ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:37Z"
    - latency: 905.53µs
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:37Z"
    - latency: 1.081111ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:37Z"
    - latency: 944.514µs
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:37Z"
    - latency: 1.271638ms
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:37Z"
    - latency: 985.585µs
      message: 'network-check-target-ip-10-0-139-186: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-network-check-target-ip-10-0-141-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "67818"
    uid: ffb7f4f3-8ac9-4940-b97b-2a6400fe3600
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:28:37Z"
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.609111ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 2.59175ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 2.628809ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 2.327211ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 1.997365ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:37Z"
    - latency: 2.24623ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:37Z"
    - latency: 2.607353ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:37Z"
    - latency: 2.537595ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:37Z"
    - latency: 2.659263ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:37Z"
    - latency: 1.961949ms
      message: 'network-check-target-ip-10-0-141-82: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-network-check-target-ip-10-0-142-253
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "67819"
    uid: 75ab0be8-821e-4891-b93a-73bb441fb1f4
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:28:37Z"
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.645756ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 2.291146ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 2.569943ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 2.659195ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 2.217599ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:52:37Z"
    - latency: 2.119708ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:51:37Z"
    - latency: 2.280293ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:50:37Z"
    - latency: 2.572841ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:49:37Z"
    - latency: 2.552549ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:48:37Z"
    - latency: 2.458098ms
      message: 'network-check-target-ip-10-0-142-253: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:47:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T18:21:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-186-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-186.ec2.internal
      uid: fb41c0c7-23e9-42e6-aceb-829ad33af2a0
    resourceVersion: "68666"
    uid: d9928e77-60fc-4256-aa8a-5b628bbe7f0b
  spec:
    sourcePod: network-check-source-6f8b768455-ccz46
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:27:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176053ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 1.999026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:57:37Z"
    - latency: 914.861µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 1.997866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:56:37Z"
    - latency: 833.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 1.981427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:55:37Z"
    - latency: 1.222318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 2.210466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:54:37Z"
    - latency: 968.023µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:53:37Z"
    - latency: 1.823507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:53:37Z"
kind: List
metadata:
  resourceVersion: ""