-
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
Create CI/CD Pipeline for Azure Cloud Platform Deployment #583
Labels
Milestone
Comments
lb4368
added
enhancement
New feature or request
4-CI/CD
Relates to issues with Zuul & gating
triage
Needs evaluation by project members
labels
Jun 16, 2021
Please assign to me. |
I will be pairing up with ratnopam on this. Please add me as well. |
Please assign size L. |
Hi, please assign this to me. |
airshipbot
pushed a commit
that referenced
this issue
Dec 4, 2021
As mentioned in kubernetes-sigs/kind#2240 there was a change in the linux kernel after 5.12.2 that makes nf_conntrack_max read-only in non-init network namespaces, which prevents kind's kube-proxy container from working correctly on kind versions older than v0.11.1. This PS updates the script to download v0.11.1 to avoid this issue. If older versions are needed, the kind url can be set as an environment variable as shown in airshipctl/tools/deployment.provider_common/01_install_kind.sh. Relates-To: #583 Change-Id: Icd9e649fa112e9f6307034ec69dde5d4a7ad613d
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem description
Per issues #564 and #575 a common site type and phase plan will be created for use by all provider types. We need a CI/CD pipeline which validates end-to-end phase plan deployment of target cluster using CAPZ provider using this common site type.
Proposed change
Build a CI/CD pipeline which demonstrates successful end-to-end deployment of az-test-site leveraging the common
gating
type created via #575 and configured with phase/plan overrides specific for the CAPZ provider.The text was updated successfully, but these errors were encountered: