apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "74456"
    uid: 87621736-8607-407b-9e1b-0576bda7f707
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.077µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:54Z"
    - latency: 956.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 893.565µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 1.329893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 927.462µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 1.023866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 1.004258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:54:54Z"
    - latency: 1.047075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:53:54Z"
    - latency: 1.209481ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:52:54Z"
    - latency: 999.82µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "72481"
    uid: be92e5f2-ba3c-432f-a397-40739b9ffe70
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:17:54Z"
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.406257ms
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 6.408296ms
      message: 'load-balancer-api-external: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 3.209032ms
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 7.347523ms
      message: 'load-balancer-api-external: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 4.165484ms
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 6.07344ms
      message: 'load-balancer-api-external: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 4.871309ms
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 6.967763ms
      message: 'load-balancer-api-external: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 6.900354ms
      message: 'load-balancer-api-external: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 6.014522ms
      message: 'load-balancer-api-external: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:55:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "72480"
    uid: 7974821a-db81-4e14-8de0-7c5b35223510
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:17:54Z"
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.408085ms
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 6.364312ms
      message: 'load-balancer-api-internal: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 4.723307ms
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 7.310078ms
      message: 'load-balancer-api-internal: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 4.16944ms
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 6.028363ms
      message: 'load-balancer-api-internal: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 5.461523ms
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 7.027437ms
      message: 'load-balancer-api-internal: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 6.516602ms
      message: 'load-balancer-api-internal: tcp connection to af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 6.073023ms
      message: 'load-balancer-api-internal: resolved host name af64cb3ba45f842f0997e38417c14730-22deebd74591a231.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:55:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-129-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "74454"
    uid: a40a3f27-9c34-4856-a259-d062f99c6969
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:54Z"
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.237558ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:54Z"
    - latency: 2.177898ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 1.76971ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 2.35605ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 2.34947ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 2.114253ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 2.617512ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:54:54Z"
    - latency: 2.496914ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:53:54Z"
    - latency: 2.58735ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:52:54Z"
    - latency: 2.375495ms
      message: 'network-check-target-ip-10-0-129-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-132-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "74455"
    uid: 2238602f-7ecb-4819-9f15-527cf9f9c483
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:54Z"
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.296515ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:54Z"
    - latency: 941.491µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 923.078µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 1.141557ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 1.094546ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 1.143517ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 1.446078ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:54:54Z"
    - latency: 955.946µs
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:53:54Z"
    - latency: 1.026543ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:52:54Z"
    - latency: 1.300281ms
      message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-ip-10-0-135-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "74453"
    uid: 2fb53e13-eed7-4dd4-99ab-ff03be33b13d
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:18:54Z"
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.176263ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T18:00:54Z"
    - latency: 2.548569ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 2.06338ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 2.384148ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 2.290106ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 2.146302ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 2.304318ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:54:54Z"
    - latency: 2.938724ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:53:54Z"
    - latency: 2.229226ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:52:54Z"
    - latency: 2.396091ms
      message: 'network-check-target-ip-10-0-135-73: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:51:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T17:11:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-11.ec2.internal
      uid: bbddfee5-3b1f-4202-9ca8-9d6e2c26ac9c
    resourceVersion: "72479"
    uid: 7b2073d6-7557-4ad3-8773-61472ee6f6af
  spec:
    sourcePod: network-check-source-7d88cb55d8-xx7xr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T17:17:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.089124ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 1.816416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:59:54Z"
    - latency: 889.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 1.887156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:58:54Z"
    - latency: 871.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 1.723403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:57:54Z"
    - latency: 1.206721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 2.026704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:56:54Z"
    - latency: 1.19801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T17:55:54Z"
    - latency: 1.778296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T17:55:54Z"
kind: List
metadata:
  resourceVersion: ""