-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Enable Kubespray deployment on vagrant #8697
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: oomichi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Testing this at local env /hold |
Current ansible.tags 'facts' is for skipping actual Kubespray deployment at vagrant CI because the deployment takes much time. However the static 'facts' skips the deployment for normal usage of vagrant also. That causes confusions. This adds VAGRANT_ANSIBLE_TAGS to skip the deployment for vagrant CI.
succeeded to pass a test locally. /hold cancel |
Thanks @oomichi ! /lgtm |
* master: (21 commits) Add tz to kubespray image Add tag to AWS VPC subnets for automatic subnet discovery by load balancers or ingress controllers (kubernetes-sigs#8705) Enable external CA mode for control-plane deployment (kubernetes-sigs#8620) UpCloud integration (kubernetes-sigs#8653) Fixes for Hetzner terraform and Hetzner Cloud (kubernetes-sigs#8702) Add VAGRANT_ANSIBLE_TAGS for normal deployment (kubernetes-sigs#8697) Removed quotation of nerdctl_extra_flags. (kubernetes-sigs#8695) [calico] add calico apiserver (kubernetes-sigs#8690) Add support for kube-vip (kubernetes-sigs#8669) Ensure all Kubelet required kernel values are configured when enabling protectKernelDefaults (kubernetes-sigs#8692) [cert-manager] Upgrade to v1.8.0 (kubernetes-sigs#8688) fix: reset docker was not removing docker properly (kubernetes-sigs#8680) Single quotes are missing in jsonpath argument of kubectl get node (kubernetes-sigs#8683) split kube_feature_gates variable for different kubernetes components (kubernetes-sigs#8677) [crun] upgrade to 1.4.4 (kubernetes-sigs#8675) [validate-container-engine] check if kubelet is present was not working (kubernetes-sigs#8679) [containerd] upgrade versions to address CVE-2022-24769 (kubernetes-sigs#8671) [vsphere_csi] update to 2.5.1 and make external_vsphere_version 7.0u1 by default (kubernetes-sigs#8676) [runc] upgrade to 1.1.1 (kubernetes-sigs#8674) [nerdctl] upgrade to 0.18.0 (kubernetes-sigs#8672) ...
Current ansible.tags 'facts' is for skipping actual Kubespray deployment at vagrant CI because the deployment takes much time. However the static 'facts' skips the deployment for normal usage of vagrant also. That causes confusions. This adds VAGRANT_ANSIBLE_TAGS to skip the deployment for vagrant CI.
Current ansible.tags 'facts' is for skipping actual Kubespray deployment at vagrant CI because the deployment takes much time. However the static 'facts' skips the deployment for normal usage of vagrant also. That causes confusions. This adds VAGRANT_ANSIBLE_TAGS to skip the deployment for vagrant CI.
Current ansible.tags 'facts' is for skipping actual Kubespray deployment at vagrant CI because the deployment takes much time. However the static 'facts' skips the deployment for normal usage of vagrant also. That causes confusions. This adds VAGRANT_ANSIBLE_TAGS to skip the deployment for vagrant CI.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Current ansible.tags 'facts' is for skipping actual Kubespray deployment at vagrant CI
because the deployment takes much time.
However the static 'facts' skips the deployment for normal usage of vagrant also.
That causes confusions.
This adds VAGRANT_ANSIBLE_TAGS to skip the deployment for vagrant CI.
Which issue(s) this PR fixes:
Fixes #8682
Does this PR introduce a user-facing change?: