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.

GITLAB_KAS_VERSION

-f48b28ef570a270b659aee53320959cffb2cebdb
+2f84f1083ebc22f6efe3ab00355ef5170bcbc142