apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "22620"
    uid: 25efac6a-e072-4e74-a199-4ab5c6ea17e5
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:43:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:43:29Z"
    - latency: 1.310718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 1.124088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 1.270978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 895.563µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 930.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 976.034µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "21255"
    uid: 95d23ffe-660b-4f85-bc4c-03fc9733626d
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:42:29Z"
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.33153ms
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 12.314317ms
      message: 'load-balancer-api-external: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 4.850727ms
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 8.425436ms
      message: 'load-balancer-api-external: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 4.73742ms
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 14.789864ms
      message: 'load-balancer-api-external: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 5.400195ms
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 7.814141ms
      message: 'load-balancer-api-external: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 6.021641ms
      message: 'load-balancer-api-external: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 7.653695ms
      message: 'load-balancer-api-external: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:38:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "21254"
    uid: c9d8aa10-ac4f-4b12-adab-f1821514f1bb
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:42:29Z"
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.314597ms
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 12.211956ms
      message: 'load-balancer-api-internal: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 4.881993ms
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 8.317706ms
      message: 'load-balancer-api-internal: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 6.309119ms
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 14.734256ms
      message: 'load-balancer-api-internal: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 5.400206ms
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 7.797596ms
      message: 'load-balancer-api-internal: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 6.0108ms
      message: 'load-balancer-api-internal: tcp connection to a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 7.590657ms
      message: 'load-balancer-api-internal: resolved host name a2100279e32344b8dabd4be432490089-c9b00160d0adb366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:38:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-130-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "22618"
    uid: a69b0d6c-186c-4307-be0a-6bc01d62a3b3
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:43:29Z"
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.905144ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:43:29Z"
    - latency: 1.775875ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 1.977266ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 2.192332ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 2.039113ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 2.008661ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 2.369953ms
      message: 'network-check-target-ip-10-0-130-136: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-140-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "22617"
    uid: 06a4e37d-8443-4e41-9b1e-388e3d3d634d
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:43:29Z"
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286742ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:43:29Z"
    - latency: 1.856496ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 2.258356ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 2.146777ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 2.200828ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 1.910512ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 2.241196ms
      message: 'network-check-target-ip-10-0-140-115: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-ip-10-0-143-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "22616"
    uid: 2664ce33-a0a2-4029-8f92-47c7c43703ec
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:43:29Z"
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.16132ms
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:43:29Z"
    - latency: 932.139µs
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 1.389373ms
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 1.804538ms
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 1.688278ms
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 742.378µs
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 1.291794ms
      message: 'network-check-target-ip-10-0-143-146: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:37:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T14:36:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-146.ec2.internal
      uid: 16d1dfa5-5738-42eb-929f-93fb184d884a
    resourceVersion: "21253"
    uid: 45b55615-643e-418e-a80e-d973b93434eb
  spec:
    sourcePod: network-check-source-989f8b8dc-hkxn9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T14:42:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.177µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 1.7501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:42:29Z"
    - latency: 1.340397ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 1.775965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:41:29Z"
    - latency: 1.341066ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 2.176071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:40:29Z"
    - latency: 1.150227ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 2.088532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:39:29Z"
    - latency: 682.445µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T14:38:29Z"
    - latency: 1.993331ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T14:38:29Z"
kind: List
metadata:
  resourceVersion: ""