-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify the k8scontrol function to deploy Calico via function #303
Comments
Related Change #743402Subject: Added function to support deployment of calico CNI ApprovalsCode-Review
-1 Sirajudeen
Verified
! None
Workflow
-1 Sirajudeen Last Updated: 2020-07-28 16:15:05 CDT |
Related Change #743763Subject: Deploy calico via function. ApprovalsCode-Review
+1 Matt McEuen
+2 Kostyantyn Kalynovskyi
+1 Ruslan Aliev
+1 Arijit Bose
+2 Dmitry Ukov
Verified
+2 Zuul
Workflow
+1 Dmitry Ukov Last Updated: 2020-08-26 10:00:07 CDT |
* Deploy Calico to ephemeral and target via function * Removed the condition to check node ready status in 25_deploy_ephemeral_node.sh and 30_deploy_controlplane.sh. As calico is applied at a later stage, relaxed the dependency to wait for node ready status. * updated compoiste/infra for calico manifest Change-Id: Id582aec3ca402eac02d9baa2305b562c410c1bea Relates-To: #303 Relates-To: #304
A [Related Change](https://review.opendev.org/743763 was merged. This issue may be ready to close. |
The related PS (https://review.opendev.org/743763) is merged. This issue can be closed now. |
closing this as ps is merged |
Proposed change
As a deployment engineer, I want to be able to deploy the Calico CNI in a consistent & declarative fashion by leveraging the Calico function defined in manifests/function/calico.
Update the k8scontrol/controlplane.yaml to no longer apply the internet version of Calico & instead leverage the Calico function.
This issue is dependent on #302 which creates the Calico function
The text was updated successfully, but these errors were encountered: