-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Upgrade readme #11765
Upgrade readme #11765
Conversation
* Make netchecker log levels configurable * use ETCD_LOG_LEVEL
Check CentOS-Base.repo exists for CentOS 7
Made corrections in Indentation at L658 which causes kubespray execution failed with YAML to Json conversion. kubernetes-sigs#11356
- Make ansible-galaxy collection dependencies explicit - Reorganized requirements.yml - Adding required collections to galaxy.yml - Ansible 9.6.0 was yanked on Pypi - Sync pre-commit requirements with requirements.txt Signed-off-by: Bas Meijer <[email protected]>
Signed-off-by: KubeKyrie <[email protected]>
…onf (kubernetes-sigs#10948) Fixes kubernetes-sigs#10947 This patch aims to be minimal and intentionally: - does not change the generation logic for `supersede_domain` and `supersede_search` - does not change how `nameserverentries` (for NetworkManager) is built It seems like `nameserverentries` in the "Generate nameservers for resolvconf, including cluster DNS" task is built the same way as `dhclient_supersede_nameserver_entries_list`. However, `nameserverentries` in the "Generate nameservers for resolvconf, not including cluster DNS" task (below) is built differently for some reason. It includes `configured_nameservers` as well. Due to these differences, I have refrained from reusing the same building logic (`dhclient_supersede_nameserver_entries_list`) for both. If the `configured_nameservers` addition can be removed or made to apply to dhclient as well, we could potentially build a single list and then generate the `nameserverentries` and `supersede_nameserver` strings from it.
fix task failure: TASK [kubernetes-apps/network_plugin/multus : Multus | Start resources] ************************************************ fatal: [hfal12k8n1 -> {{ groups['kube_control_plane'][0] }}]: FAILED! => {"msg": "Error in jmespath.search in json_query filter plugin:\n'ansible.vars.hostvars.HostVarsVars object' has no attribute 'multus_manifest_2'"}
…kubernetes-sigs#11422) * fix: use super-admin.conf for kube-vip when it exists * Mathieu Parent add as co-author Co-authored-by: Mathieu Parent <[email protected]> * template change for readability * fix lint error --------- Co-authored-by: Mathieu Parent <[email protected]>
Bumps [tox](https://github.com/tox-dev/tox) from 4.16.0 to 4.17.1. - [Release notes](https://github.com/tox-dev/tox/releases) - [Changelog](https://github.com/tox-dev/tox/blob/main/docs/changelog.rst) - [Commits](tox-dev/tox@4.16.0...4.17.1) --- updated-dependencies: - dependency-name: tox dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Signed-off-by: Mengxin Liu <[email protected]>
Signed-off-by: ChengHao Yang <[email protected]>
Bumps [tox](https://github.com/tox-dev/tox) from 4.17.1 to 4.18.0. - [Release notes](https://github.com/tox-dev/tox/releases) - [Changelog](https://github.com/tox-dev/tox/blob/main/docs/changelog.rst) - [Commits](tox-dev/tox@4.17.1...4.18.0) --- updated-dependencies: - dependency-name: tox dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* chore(containerd): add some config debug options See: https://github.com/containerd/containerd/blob/v1.7.15/docs/man/containerd-config.toml.5.md * chore(containerd): add CRI config options See: https://github.com/containerd/containerd/blob/v1.7.15/docs/man/containerd-config.toml.5.md See: https://github.com/containerd/containerd/blob/v1.7.15/docs/cri/config.md
Makes easier diff when adding or removing plugins.
This is already handled by the previous task.
Signed-off-by: KubeKyrie <[email protected]>
Bumps [molecule](https://github.com/ansible-community/molecule) from 24.7.0 to 24.8.0. - [Release notes](https://github.com/ansible-community/molecule/releases) - [Commits](ansible/molecule@v24.7.0...v24.8.0) --- updated-dependencies: - dependency-name: molecule dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…inventory_builder Remove inventory_builder and re-organize docs
Signed-off-by: bo.jiang <[email protected]>
…igs#11751)" (kubernetes-sigs#11756) This reverts commit b1b782d.
config_path was introduced in containerd 1.5.0, and registry.mirrors is deprecated. There is no reason to keep the old alternative, so just always use config_path, and consequently remove the option.
…rnetes-sigs#11757) Signed-off-by: bo.jiang <[email protected]>
4b2bf4d (preinstall: simplify OS packages selection, 2024-11-04) removed all usages of ansible.utils.validate (not that many), so the dependencies is no longer necessary.
Those files haven't been touched in roughly 5 years, and pip install on Kubespray errors out. The 'Requires:' are outdated, which suggests that no one is using this.
…igs#11758) Signed-off-by: bo.jiang <[email protected]>
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages. The list of commits with invalid commit messages:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Adding label Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Welcome @stasmachship! |
Hi @stasmachship. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stasmachship The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Sorry about that, created a PR to wrong repo |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: