Update KAS version

Update KAS to the latest green master

What should I do if this pipeline is red?

• Look at the failure. If it looks unrelated to KAS, it's likely a master:broken or failureflaky-test.
  1. Open the Pipelines tab and click Run Pipeline.
  2. This will run a pipeline for merge result.
• If it looks related to KAS, notify the KAS team in #f_agent_for_kubernetes on Slack.

What should I do in case of merge conflicts?

If someone updates GITLAB_KAS_VERSION with another MR, we may have a merge conflict.

In such unlikely circumstances, the better option will be closing this merge request and deleting the release-tools/update-kas branch.

release-tools will take care of creating a new merge request in about 1 hour.

---

This merge request was generated via release-tools pipeline.

Do you want to improve this message? You can find it here! groupenvironments loves merge requests.

changed milestone to %17.5

added KAS automation:bot-authored groupenvironments maintenancedependency typemaintenance labels

assigned to @gitlab-release-tools-bot

added 1 commit

• 6dca3f68 - Update gitlab-agent to f900f198b8b

Compare with previous version

added pipelinetier-1 label

added devopsdeploy sectioncd labels

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for 6dca3f68

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 128    | 0      | 18      | 0     | 146   | ✅     |
| Verify      | 45     | 0      | 2       | 0     | 47    | ✅     |
| Plan        | 76     | 0      | 0       | 1     | 76    | ✅     |
| Data Stores | 33     | 0      | 1       | 0     | 34    | ✅     |
| Package     | 24     | 0      | 11      | 0     | 35    | ✅     |
| Fulfillment | 2      | 0      | 0       | 0     | 2     | ✅     |
| Secure      | 4      | 0      | 0       | 0     | 4     | ✅     |
| Govern      | 73     | 0      | 0       | 0     | 73    | ✅     |
| Release     | 5      | 0      | 0       | 0     | 5     | ✅     |
| Monitor     | 8      | 0      | 0       | 0     | 8     | ✅     |
| Manage      | 1      | 0      | 1       | 0     | 2     | ✅     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 401    | 0      | 33      | 1     | 434   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

enabled automatic add to merge train when checks pass

approved this merge request

added this merge request to the merge train at position 2

merged

mentioned in commit 245d6439

added workflowstaging-canary label

added workflowstaging label and removed workflowstaging-canary label

added workflowproduction label and removed workflowstaging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label