forked from tim/k3s-ansible
c82f2e0415
* chore(deps): apply dependency updates in one combined change - Bump ansible-core to 2.19.11 and jmespath to 1.1.0 in requirements.in - Regenerate the Python 3.11 pip-compile lock in requirements.txt - Bump molecule-plugins to 23.6.0 while keeping molecule on the stable 6.x series (avoids the molecule-plugins 26 major jump that broke vagrant module resolution in CI) - Bump ruamel-yaml-clib to 0.2.15 - Bump the zgosalvez/github-actions-ensure-sha-pinned-actions action to 5.0.6 (SHA-pinned) in lint.yml * fix(server): make log_destination conditional boolean for ansible-core 2.19 - The always block's 'Save logs of k3s-init.service' task used when: log_destination where log_destination is a path string derived from an env var - ansible-core 2.19 rejects string-derived conditionals; evaluate the path as a real boolean (non-empty) check so the conditional is a true boolean - Required to keep the k3s_server role working with ansible-core 2.19.11 (the dependency bump in this change) * fix(verify): coerce regex_search assertions to bool for ansible-core 2.19 - ansible-core 2.19 requires assert conditionals to be boolean; regex_search returns a string, which is now rejected - Wrap all regex_search results used in assert.that with | bool so the calico, cilium, metallb, and kube-vip image-tag checks produce boolean results * fix(verify): use boolean is regex_search test instead of | bool - | bool on a regex_search result coerces a tag string like v0.16.0 to False in ansible-core 2.19, failing the image-tag assertions - Use the is regex_search test which returns a real boolean without string coercion for the calico, cilium, metallb, and kube-vip image assertions * fix(verify): use is not none for regex_search assertions - ansible-core 2.19 has no "is regex_search" test and rejects bool string coercion, so use the regex_search filter with an "is not none" comparison, which yields a real boolean for the image-tag assertions - Applies to calico, cilium, metallb, and kube-vip image checks * fix(metallb): retry transient apiserver resets in config tests - The Layer 2 and BGP final configuration checks ran a kubectl get per resource with no retry, so a transient connection refused from the kube API could abort converge - Mirror the download_retries/download_delay retry pattern used by the 'Wait for MetalLB resources' task so these checks survive api server resets on slow runners
170 lines
3.2 KiB
Plaintext
170 lines
3.2 KiB
Plaintext
#
|
|
# This file is autogenerated by pip-compile with Python 3.11
|
|
# by the following command:
|
|
#
|
|
# pip-compile --output-file=requirements.txt requirements.in
|
|
#
|
|
ansible-compat==4.1.11
|
|
# via molecule
|
|
ansible-core==2.19.11
|
|
# via
|
|
# -r requirements.in
|
|
# ansible-compat
|
|
# molecule
|
|
attrs==23.2.0
|
|
# via
|
|
# jsonschema
|
|
# referencing
|
|
bracex==2.4
|
|
# via wcmatch
|
|
cachetools==5.3.2
|
|
# via google-auth
|
|
certifi==2023.11.17
|
|
# via
|
|
# kubernetes
|
|
# requests
|
|
cffi==1.16.0
|
|
# via cryptography
|
|
cfgv==3.4.0
|
|
# via pre-commit
|
|
charset-normalizer==3.3.2
|
|
# via requests
|
|
click==8.1.7
|
|
# via
|
|
# click-help-colors
|
|
# molecule
|
|
click-help-colors==0.9.4
|
|
# via molecule
|
|
cryptography==41.0.7
|
|
# via ansible-core
|
|
distlib==0.3.8
|
|
# via virtualenv
|
|
enrich==1.2.7
|
|
# via molecule
|
|
filelock==3.13.1
|
|
# via virtualenv
|
|
google-auth==2.26.2
|
|
# via kubernetes
|
|
identify==2.5.33
|
|
# via pre-commit
|
|
idna==3.6
|
|
# via requests
|
|
jinja2==3.1.3
|
|
# via
|
|
# ansible-core
|
|
# molecule
|
|
jmespath==1.1.0
|
|
# via -r requirements.in
|
|
jsonpatch==1.33
|
|
# via -r requirements.in
|
|
jsonpointer==2.4
|
|
# via jsonpatch
|
|
jsonschema==4.21.1
|
|
# via
|
|
# ansible-compat
|
|
# molecule
|
|
jsonschema-specifications==2023.12.1
|
|
# via jsonschema
|
|
kubernetes==29.0.0
|
|
# via -r requirements.in
|
|
markdown-it-py==3.0.0
|
|
# via rich
|
|
markupsafe==2.1.4
|
|
# via jinja2
|
|
mdurl==0.1.2
|
|
# via markdown-it-py
|
|
molecule==6.0.3
|
|
# via
|
|
# -r requirements.in
|
|
# molecule-plugins
|
|
molecule-plugins[vagrant]==23.6.0
|
|
# via -r requirements.in
|
|
netaddr==0.10.1
|
|
# via -r requirements.in
|
|
nodeenv==1.8.0
|
|
# via pre-commit
|
|
oauthlib==3.2.2
|
|
# via
|
|
# kubernetes
|
|
# requests-oauthlib
|
|
packaging==23.2
|
|
# via
|
|
# ansible-compat
|
|
# ansible-core
|
|
# molecule
|
|
platformdirs==4.1.0
|
|
# via virtualenv
|
|
pluggy==1.3.0
|
|
# via molecule
|
|
pre-commit==3.8.0
|
|
# via -r requirements.in
|
|
pre-commit-hooks==4.6.0
|
|
# via -r requirements.in
|
|
pyasn1==0.5.1
|
|
# via
|
|
# pyasn1-modules
|
|
# rsa
|
|
pyasn1-modules==0.3.0
|
|
# via google-auth
|
|
pycparser==2.21
|
|
# via cffi
|
|
pygments==2.17.2
|
|
# via rich
|
|
python-dateutil==2.8.2
|
|
# via kubernetes
|
|
python-vagrant==1.0.0
|
|
# via molecule-plugins
|
|
pyyaml==6.0.2
|
|
# via
|
|
# -r requirements.in
|
|
# ansible-compat
|
|
# ansible-core
|
|
# kubernetes
|
|
# molecule
|
|
# pre-commit
|
|
referencing==0.32.1
|
|
# via
|
|
# jsonschema
|
|
# jsonschema-specifications
|
|
requests==2.31.0
|
|
# via
|
|
# kubernetes
|
|
# requests-oauthlib
|
|
requests-oauthlib==1.3.1
|
|
# via kubernetes
|
|
resolvelib==1.0.1
|
|
# via ansible-core
|
|
rich==13.7.0
|
|
# via
|
|
# enrich
|
|
# molecule
|
|
rpds-py==0.17.1
|
|
# via
|
|
# jsonschema
|
|
# referencing
|
|
rsa==4.9
|
|
# via google-auth
|
|
ruamel-yaml==0.18.5
|
|
# via pre-commit-hooks
|
|
ruamel-yaml-clib==0.2.15
|
|
# via ruamel-yaml
|
|
six==1.16.0
|
|
# via
|
|
# kubernetes
|
|
# python-dateutil
|
|
subprocess-tee==0.4.1
|
|
# via ansible-compat
|
|
urllib3==2.1.0
|
|
# via
|
|
# kubernetes
|
|
# requests
|
|
virtualenv==20.25.0
|
|
# via pre-commit
|
|
wcmatch==8.5
|
|
# via molecule
|
|
websocket-client==1.7.0
|
|
# via kubernetes
|
|
|
|
# The following packages are considered to be unsafe in a requirements file:
|
|
# setuptools
|