0d29292e00
This patch replaces the "kuryr-kubernetes" handling used by tacker's FT to build the k8s environment with "devstack-plugin-container". Also, with the update of devstack-plugin-container, k8s, cri-o and helm will be upgraded. k8s: 1.26.8 -> 1.30.5 crio: 1.26 -> 1.30.5 helm: 3.11.3 -> 3.15.4 The following is a summary of the fixes in this patch. * Remove plugins and settings related to kuryr-kubernetes * Rename parameters with "kuryr" * Modify devstack-plugin-container to be used in FT k8s environment build * Add parameters required by devstack-plugin-container Also, the following is a list of problems that occurred when setting up the k8s environment with devstack-plugin-container and how to fix them. Cannot get bearer_token value: - modified file: roles/setup-default-vim/tasks/main.yaml - The task "Get admin token from described secret" of the Ansible role "setup-default-vim" failed to obtain the value of bearer_token, which is set as a parameter when creating vim, causing an error. Retrying to obtain token fixed the problem. Unknown error in "Create clusterrolebinding on k8s server" task: - modified file: roles/setup-k8s-nodes/tasks/main.yaml - In task "Create clusterrolebinding on k8s server" in Ansible role "setup-k8s-oidc", `failed to download openapi: unknown;` error occurred. The cause was that the pod status of kube-apiserver was "Pending" after executing the previous "Wait for k8s apiserver to restart" task. The error was fixed by waiting for the Pod status to reach the "Running" state. "cni0" is not assigned the intended IP address: - added file: roles/restart-kubelet-service/tasks/main.yaml - When using devstack-plugin-container to create a k8s environment and deploy a Pod, the Pod deployment fails with the error `network: failed to set bridge addr: "cni0" already has an IP address different from 10.x.x.x`. Removing the associated interface and restarting the service cleared the error. Depends-On: https://review.opendev.org/c/openstack/devstack-plugin-container/+/926709 Change-Id: I596a2339f6a3c78fee99b92d7bfb65a6b0244901
Tacker
Welcome!
Tacker is an OpenStack based NFV Orchestrator service with built-in general purpose VNF Manager to deploy and operate Virtual Network Functions (VNFs) on an OpenStack based NFV Platform. It is based on ETSI MANO Architectural Framework and provides a fully functional stack to orchestrate VNFs end-to-end.
Installation:
Installation instructions and user guides can be found at: https://docs.openstack.org/tacker/
Tacker code base supports OpenStack master and other releases. Please follow the instructions in the above address for a successful installation of corresponding release.
Code:
Tacker code is available in following repositories:
- Tacker server: https://opendev.org/openstack/tacker
- Tacker Python client: https://opendev.org/openstack/python-tackerclient
- Tacker Horizon UI: https://opendev.org/openstack/tacker-horizon
Bugs:
Please report bugs at: https://bugs.launchpad.net/tacker
External Resources:
- Tacker Wiki: https://wiki.openstack.org/wiki/Tacker
- Tacker Blueprints: https://blueprints.launchpad.net/tacker
- For help on usage and hacking of Tacker, please send an email to OpenStack-dev Mailing List <mailto:openstack-discuss@lists.openstack.org> with [openstack-dev] [Tacker] tag.
- To get release notes: Tacker Release Notes