apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "24470"
    uid: b07b99c1-e724-467e-b8b8-49e5d9c22961
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:33:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:33:46Z"
    - latency: 1.433021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:32:46Z"
    - latency: 1.063961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:31:46Z"
    - latency: 1.072313ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:30:46Z"
    - latency: 1.034394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:29:46Z"
    - latency: 1.143405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:28:46Z"
    - latency: 1.152437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "28747"
    uid: 8a5abfd2-067f-491f-b47a-8a44c0ca0c44
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:32:46Z"
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.140187ms
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 8.107906ms
      message: 'load-balancer-api-external: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 5.280959ms
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 6.789532ms
      message: 'load-balancer-api-external: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 3.265148ms
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 6.809891ms
      message: 'load-balancer-api-external: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 5.005358ms
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 8.384432ms
      message: 'load-balancer-api-external: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 4.113212ms
      message: 'load-balancer-api-external: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:34:46Z"
    - latency: 6.798289ms
      message: 'load-balancer-api-external: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:34:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "28746"
    uid: 64519113-ce56-4e92-aa75-091debe70301
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:32:46Z"
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.066833ms
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 8.021439ms
      message: 'load-balancer-api-internal: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 4.814766ms
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 6.9039ms
      message: 'load-balancer-api-internal: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 3.912138ms
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 6.835068ms
      message: 'load-balancer-api-internal: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 5.051798ms
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 8.299858ms
      message: 'load-balancer-api-internal: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 4.085216ms
      message: 'load-balancer-api-internal: tcp connection to aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:34:46Z"
    - latency: 6.721996ms
      message: 'load-balancer-api-internal: resolved host name aaf204cbed961455f913615d1749957e-e07097ca4401f14a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:34:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-network-check-target-ip-10-0-132-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "24467"
    uid: dc620ab5-5e62-4c8f-975e-8f75cb845988
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:33:46Z"
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.815585ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:33:46Z"
    - latency: 1.977594ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:32:46Z"
    - latency: 2.069807ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:31:46Z"
    - latency: 2.063664ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:30:46Z"
    - latency: 2.055761ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:29:46Z"
    - latency: 1.893171ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:28:46Z"
    - latency: 1.995172ms
      message: 'network-check-target-ip-10-0-132-113: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-network-check-target-ip-10-0-142-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "24468"
    uid: 012f4b1b-ca10-4c3c-885e-7e962e232251
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:33:46Z"
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.000807ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:33:46Z"
    - latency: 2.324477ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:32:46Z"
    - latency: 1.900437ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:31:46Z"
    - latency: 2.119282ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:30:46Z"
    - latency: 2.324702ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:29:46Z"
    - latency: 2.153715ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:28:46Z"
    - latency: 2.330098ms
      message: 'network-check-target-ip-10-0-142-246: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-network-check-target-ip-10-0-143-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "24466"
    uid: a5b7e1b0-f76c-4854-ae62-1876e33dfe87
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:33:46Z"
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051944ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:33:46Z"
    - latency: 909.853µs
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:32:46Z"
    - latency: 895.77µs
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:31:46Z"
    - latency: 902.773µs
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:30:46Z"
    - latency: 1.013787ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:29:46Z"
    - latency: 1.346154ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:28:46Z"
    - latency: 1.525484ms
      message: 'network-check-target-ip-10-0-143-130: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:27:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T19:26:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-130-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-130.ec2.internal
      uid: 22d89249-ac47-4136-8df2-0c1e0d0fb766
    resourceVersion: "28743"
    uid: 31c21c83-eeb2-4e83-822f-bba010da480e
  spec:
    sourcePod: network-check-source-dbd9cf844-9mnqr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T19:32:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090438ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 2.304929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:38:46Z"
    - latency: 844.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 1.840443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:37:46Z"
    - latency: 1.226404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 1.702105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:36:46Z"
    - latency: 936.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 1.991492ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:35:46Z"
    - latency: 906.839µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T19:34:46Z"
    - latency: 1.810071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T19:34:46Z"
kind: List
metadata:
  resourceVersion: ""