-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): update helm release cluster to v4.6.0 #1601
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
base: main
Are you sure you want to change the base?
Conversation
6d8fde7 to
315aac4
Compare
315aac4 to
6f6a5a8
Compare
|
/run cluster-test-suites |
|
There were differences in the rendered Helm template, please check! Output |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
cluster-test-suites
❌ Failed test suitesCAPA Standard Suite ❌
📋 View full results in Tekton Dashboard Rerun trigger: Important Save time and costs - re-run only the failed tests: Available Test SuitesBy default, only the standard test suite runs to reduce costs. If your changes affect specialized environments, you can specify additional test suites: AWS (CAPA) Test Suites
How to Specify Additional Test Suites# Run specific test suites
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard,./providers/capa/china
# Run all test suites for CAPA
/run cluster-test-suites TARGET_SUITES=./providers/capa/
# Run upgrade tests
/run cluster-test-suites TARGET_SUITES=./providers/capa/upgrade,./providers/capa/upgrade-majorNote: Full test suites run automatically on releases. You are responsible for testing all relevant flavors before merging. |
|
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard |
cluster-test-suites
❌ Failed test suitesCAPA Standard Suite ❌
📋 View full results in Tekton Dashboard Rerun trigger: Important Save time and costs - re-run only the failed tests: Available Test SuitesBy default, only the standard test suite runs to reduce costs. If your changes affect specialized environments, you can specify additional test suites: AWS (CAPA) Test Suites
How to Specify Additional Test Suites# Run specific test suites
/run cluster-test-suites TARGET_SUITES=./providers/capa/standard,./providers/capa/china
# Run all test suites for CAPA
/run cluster-test-suites TARGET_SUITES=./providers/capa/
# Run upgrade tests
/run cluster-test-suites TARGET_SUITES=./providers/capa/upgrade,./providers/capa/upgrade-majorNote: Full test suites run automatically on releases. You are responsible for testing all relevant flavors before merging. |
|
@giantswarm/team-atlas Can you please check what's wrong with Mimir on |
|
Ah, yeah, daily cluster test suites are failing for the same reason. And they use a released |
This PR contains the following updates:
4.5.1->4.6.0Release Notes
giantswarm/cluster (cluster)
v4.6.0Compare Source
Changed
config_path(/etc/containerd/certs.d) andhosts.tomlfor registry mirrors, ensuring proper fallback order (local cache -> mirrors -> upstream).hosts.tomlheaders, asregistry.configsis ignored whenconfig_pathis enabled.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.