Update dependency kas to v17.0.0-rc4

This MR contains the following updates:

Package	Update	Change
kas	patch	v17.0.0-rc3 -> v17.0.0-rc4

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

---

Release Notes

gitlab-org/cluster-integration/gitlab-agent (kas)

v17.0.0-rc4

Compare Source

Release for tag v17.0.0-rc4

---

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot.

Renovate Comment

kas version update MR

This Merge Request has been created with the help of renovate-gitlab-bot project.

This MR is part of GitLab Agent for Kubernetes release process. It updates the version of the server component of the agent - kas.

FYI @partiaga, @tigerwnz, @ash2k, @timofurrer, @hustewart, @takax.

Troubleshooting

We have assembled some FAQs to help reviewers of these kind of merge requests.

Improve this message – The JSON comment below is for automation purposes.

{"labels":["maintenance::dependency","type::maintenance","automation:bot-authored","group::environments","devops::deploy","section::cd","KAS"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["ash2k","timofurrer"]}

mentioned in issue #390663 (closed)

added KAS automation:bot-authored devopsdeploy groupenvironments maintenancedependency sectioncd typemaintenance labels

requested review from @timofurrer and @ash2k

assigned to @gitlab-dependency-update-bot

added 1 commit

• 159ccbdc - Update dependency kas to v17.0.0-rc4

Compare with previous version

approved this merge request

added pipeline:mr-approved label

@ash2k, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, a new pipeline will be started shortly.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

resolved all threads

merged

@ash2k, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:

1. Ensure the merge request is not in Draft status.
2. Start a pipeline (especially important for Community contribution merge requests).
3. Set the merge request to auto-merge.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.

mentioned in commit b2ab3eff

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 159ccbdc

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Verify      | 31     | 0      | 1       | 30    | 32    | ✅     |
| Package     | 19     | 0      | 12      | 19    | 31    | ✅     |
| Plan        | 52     | 0      | 2       | 47    | 54    | ✅     |
| Govern      | 66     | 0      | 0       | 43    | 66    | ✅     |
| Create      | 101    | 0      | 9       | 94    | 110   | ✅     |
| Monitor     | 7      | 0      | 0       | 7     | 7     | ✅     |
| Data Stores | 31     | 0      | 0       | 22    | 31    | ✅     |
| Analytics   | 2      | 0      | 0       | 1     | 2     | ✅     |
| Release     | 5      | 0      | 0       | 5     | 5     | ✅     |
| Manage      | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 314    | 0      | 25      | 268   | 339   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

changed milestone to %17.1

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#6248 (closed)

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#6249 (closed)

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#6251 (closed)

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label