Skip to content

Outlined our code's incompatibility with Google KMS encryption

Vlad Stoianovici requested to merge docs_vstoianovici_gcp_kms into master

What does this MR do?

Outline the fact that Google's KMS bucket encryption is not currently supported and has caused confusion for customers - ZD: https://gitlab.zendesk.com/agent/tickets/229481 (internal)

Related issues

gitlab-org/charts/gitlab#1564 (closed)

Author's checklist

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Vlad Stoianovici

Merge request reports

Loading