Deprecation and Removal of ca-cert-file cli option in favor of kas-ca-cert-file in agentk

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Release notes

In the GitLab Agent for Kubernetes (agentk) the --ca-cert-file command line option and the corresponding config.caCert Helm Chart Value have been renamed to --kas-ca-cert-file and config.kasCaCert, respectively. In 17.0, the old --ca-cert-file and config.caCert options will be removed. Until then, they are deprecated, but continue to work.

https://docs.gitlab.com/ee/user/clusters/agent/install/#install-the-agent-with-helm

Deprecation Summary

The GitLab Agent for Kubernetes (agentk) introduced a new kas-ca-cert-file command line option which replaces the old ca-cert-file option. It's a simple rename without any additional logic.

Breaking Change

The user can update their invocation of agentk by using the new kas-ca-cert-file flag or use the corresponding Helm value.

Affected Topology

Affected Tier

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @cfoster3
  • Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

Planned Removal Milestone

Links

Edited by Timo Furrer