Hi. Where you put "/.kube/config" inside the containers. Nguyen Huu Khoi On Sun, Dec 17, 2023 at 4:25 PM Satish Patel <satish.txt@gmail.com> wrote:
Thank you,
I am stuck here.. I have build kind cluster outside kolla-ansible and copy ~/.kube/config to magnum_api and conductor container as per documented and when trying to create cluster getting following error # openstack coe cluster show mycluster2
+----------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +----------------------+-----------------------------------------------------------------------------------------------------------------------------------------+ | status | CREATE_FAILED | | health_status | None | | cluster_template_id | 2ddfdf2a-5962-42ee-a2e2-ff9e0b19dbe5 | | node_addresses | [] | | uuid | abf42808-d67c-450e-88e0-a20e65f35232 | | stack_id | kube-a0lo8 | | status_reason | 404 Client Error: Not Found for url: https://192.168.18.234:6443/apis/infrastructure.cluster.x-k8s.io/v1alpha7/na... | | | system/openstackmachinetemplates/magnum-v0.13.0?fieldManager=atmosphere-operator&force=True | | created_at | 2023-12-17T09:16:05+00:00 | | updated_at | 2023-12-17T09:16:11+00:00 | | coe_version | None | | labels | {'kube_tag': 'v1.27.4'} | | labels_overridden | {} | | labels_skipped | {} | | labels_added | {} | | fixed_network | None | | fixed_subnet | None | | floating_ip_enabled | True | | faults | {} | | keypair | None | | api_address | None | | master_addresses | [] | | master_lb_enabled | False | | create_timeout | 60 | | node_count | 1 | | discovery_url | None | | docker_volume_size | None | | master_count | 1 | | container_version | None | | name | mycluster2 | | master_flavor_id | m1.medium | | flavor_id | m1.medium | | health_status_reason | {} | | project_id | 08cae850a5bb47d998da180a7f0e2660 | +----------------------+-----------------------------------------------------------------------------------------------------------------------------------------+
I have kind cluster configured as per documented
# kubectl get namespaces NAME STATUS AGE capi-kubeadm-bootstrap-system Active 11h capi-kubeadm-control-plane-system Active 11h capi-system Active 11h capo-system Active 11h cert-manager Active 11h default Active 11h kube-node-lease Active 11h kube-public Active 11h kube-system Active 11h local-path-storage Active 11h magnum-system Active 11h
# kubectl get deployment --all-namespaces NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE capi-kubeadm-bootstrap-system capi-kubeadm-bootstrap-controller-manager 1/1 1 1 11h capi-kubeadm-control-plane-system capi-kubeadm-control-plane-controller-manager 1/1 1 1 11h capi-system capi-controller-manager 1/1 1 1 11h capo-system capo-controller-manager 1/1 1 1 11h cert-manager cert-manager 1/1 1 1 11h cert-manager cert-manager-cainjector 1/1 1 1 11h cert-manager cert-manager-webhook 1/1 1 1 11h kube-system coredns 2/2 2 2 11h local-path-storage local-path-provisioner 1/1 1 1 11h
What did I miss?
On Sun, Dec 17, 2023 at 4:12 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hi. I setup a k8s cluster managent by kubespray.
About load, we can scale up or scale out our k8s node. just monitor it and you will know how to do.