Ingress Nginx Integration setup ingress using node-port & reverse proxy Change-Id: I4d1241616ebc07f5d9f09da7871282c96cd41062
package v2 ubuntu image offline deployment should use v2 image v2 image has partitioning utils Change-Id: I9ae9a49e5571dbea90d0e4f6376ab3facab16c0a
k8s version 1.19.11 change k8s verion 1.19.11 supporting kubespray verion 2.16 k8s 1.19.11 is required by onap istanbul update helm to 3.5.4 Depends-On: If212fba441ed53f7a95185a6103f2f1c48cbcd74 Change-Id: Id59f5e83cdc6efb8b8795122e599af772ca659ae
Update rook-ceph kubernetes deployment * Upgrade rook to v1.5.9 (and update associated CRDs) * Upgrade ceph to latest release * Add taints and tolerations to separate rook-ceph workloads from other workloads to work around RBD+XFS hangup bug * Use a separate volume for Ceph block storage Signed-off-by: Cian Johnston <cian.johnston@est.tech> Change-Id: I3a634204ab63183adb137d9c07bf026b16ec2fcf Signed-off-by: Cian Johnston <cian.johnston@est.tech>
Update Helm to version 3.3.4 * helm_version -> v3.3.4 * required changes to Helm CLI invocations Change-Id: I4816a6da5da50d039d5cf77717d8d33797ff0d6e Signed-off-by: Cian Johnston <cian.johnston@est.tech>
Package busybox container image for ceph workaround Busybox image is not packaged for offline deployments, causing pod to fail coming up as the image is not available in local docker registry. Adding image to list of images to pull and package. Busybox repo in the install template is also updated in order to get rid of duplicated path and adjust it based on the path it gets on local registry. Warning Failed 118s (x4 over 3m56s) kubelet, master0 Failed to pull image "engine.local/library/busybox/library/busybox:1.32.0": rpc error: code = Unknown desc = Error response from daemon: manifest for engine.local/library/busybox/library/busybox:1.32.0 not found Change-Id: Ibc173049c1bae5676dde2a686bd6092761dc645d
Bump kubernetes to v1.18.5 The container image, flannel_cni, is removed in upstream Kubespray download role so we remove it as well. Depends-On: Ie8be93ba62dc90229f54bd618c982aeaf4bdaafb Change-Id: I7bc9f42fd5bb6a29d4dd16d9e56228dde58fd498
Control docker version within stack Docker version was originally controlled within engine repository but it is more appropriate to control it within the stack as the version requirements could be different across the stacks. See the dependent change for how it was controlled before. Depends-On: Id5f2c72e35bba4d5ab413f7b19119330540f5674 Change-Id: I2720d6b6ddcde0f742f527e3f86b3085f13aaeda
Create engine kubernetes stack This change creates kubernetes stack for engine in order to package, deploy, and test stacks independently from engine core. The main feature this enables is the ability to develop stacks in their own repository with proper versioning and branching no matter how the tools (provisioner and installer) are developed. The stack simply selects versions of the tools (could be branches) and the rest is done accordingly. The role package which was previously located under infra/installer/kubespray is moved into this repository in order to handle what to package within the stack since some of the artifacts we package do not belong to installer but to the stack itself. Change-Id: I760d4d904544dad768525e999ebe53e156464111