Commit d7f38586 authored by Nicole Schwartz's avatar Nicole Schwartz
Browse files

Release post - GitLab 14.3

parent ad23ae9e
- version: "14.3"
name: "feistel"
gitlab: feistel
date: "September 22, 2021"
- version: "14.2"
name: "Cornelius Ludmann"
gitlab: corneliusludmann
......
......@@ -4,11 +4,11 @@ features:
available_in: [premium, ultimate]
gitlab_com: true
documentation_link: 'https://docs.gitlab.com/ee/user/clusters/agent/repository.html#authorize-groups-to-use-an-agent'
video: 'https://www.youtube.com/embed/zf_QTU149ng'
video: 'https://www.youtube-nocookie.com/embed/zf_QTU149ng'
reporter: nagyv-gitlab
stage: configure
categories:
- Kubernetes Management
epic_url: 'https://gitlab.com/groups/gitlab-org/-/epics/5784'
description: |
The GitLab Kubernetes Agent provides a secure connection between a Kubernetes cluster and GitLab. Until GitLab 14.2, the CI/CD Tunnel enabled pushing to a cluster only from the same project where the Kubernetes Agent was registered. GitLab 14.3, the Agent can be authorized to access entire groups. As a result, every project under the authorized group has access to the cluster without the need to register an agent for every project.
The GitLab Kubernetes Agent provides a secure connection between a Kubernetes cluster and GitLab. Until GitLab 14.2, the CI/CD Tunnel enabled pushing to a cluster only from the same project where the Kubernetes Agent was registered. In GitLab 14.3, the Agent can be authorized to access entire groups. As a result, every project under the authorized group has access to the cluster without the need to register an agent for every project.
......@@ -3,15 +3,15 @@ features:
- name: "Preview multimedia in the new Wiki editor"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/wiki/#gitlab-flavored-markdown-support'
image_url: '/images/unreleased/audio-video-in-wiki-editor.png'
image_url: '/images/14_3/audio-video-in-wiki-editor.png'
reporter: ericschurter
stage: create
categories:
- 'Wiki'
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/332074'
description: |
Including multimedia in a wiki page is a great way to effectively and efficiently communicate complex content. GitLab Flavored Markdown supports embedding [video and audio content](https://docs.gitlab.com/ee/user/markdown.html#videos) for playback. However, when you're editing the page, the media is represented in code by the path to the file, and that can lead to confusion or uncertainty around whether you uploaded the right version of the file.
In GitLab 14.3, the new WYSIWYG Markdown editor in the Wiki renders and plays back existing video and audio content on the page right in the editor. Now you can be sure that the `recording_final.mp3` or `walkthrough.mp4` you attached is indeed the right asset without leaving the editor. Currently, this only applies to media already included in the page when it's loaded into the editor. We will add support for [inserting new video and audio content](https://gitlab.com/gitlab-org/gitlab/-/issues/332088) from the editor in an upcoming milestone.
Including multimedia in a wiki page is a great way to effectively and efficiently communicate complex content. GitLab Flavored Markdown supports embedding [video and audio content](https://docs.gitlab.com/ee/user/markdown.html#videos) for playback. However, when you're editing the page, the media is represented in code by the path to the file, and that can lead to confusion or uncertainty around whether you uploaded the right version of the file.
In GitLab 14.3, the new WYSIWYG Markdown editor in the Wiki renders and plays back existing video and audio content on the page right in the editor. Now you can be sure that the `recording_final.mp3` or `walkthrough.mp4` you attached is indeed the right asset without leaving the editor. Currently, this only applies to media already included in the page when it's loaded into the editor. We will add support for [inserting new video and audio content](https://gitlab.com/gitlab-org/gitlab/-/issues/332088) from the editor in an upcoming milestone.
 
Thanks to [Lee Tickett](https://gitlab.com/leetickett) for this helpful contribution!
......@@ -5,7 +5,7 @@ features:
available_in: [core, premium, ultimate]
gitlab_com: true
documentation_link: 'https://docs.gitlab.com/ee/user/project/wiki/#content-editor'
image_url: '/images/unreleased/wiki-editor-edit-table-structure.png'
image_url: '/images/14_3/wiki-editor-edit-table-structure.png'
reporter: ericschurter
stage: create
categories:
......@@ -13,5 +13,5 @@ features:
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/328759'
description: |
Editing a Markdown table that has 9 columns and 25 rows is one thing. But adding a tenth column to that table in Markdown? That involves very repetitive and error-prone edits to every row. One mistake or misplaced `|` and the table fails to render.
The new WYSIWYG Markdown editor in the wiki lets you quickly and easily insert a table using the button in the toolbar. After selecting the initial number of rows and columns, however, dealing with the structure of the table can be more difficult. In GitLab 14.3, you can now click on the caret icon in the top right corner of any selected cell to add or remove columns and rows, either before or after the selected cell. Now, as your content scales, the complexity doesn't follow suit.
---
cta:
- title: "Join us for an upcoming event" # default
link: '/events/'
deprecations:
- feature_name: "NFS for Git repository storage deprecated"
due: Jun 22, 2022
reporter: mjwood
description: |
With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS in GitLab 15.0. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information.
Gitaly Cluster offers tremendous benefits for our customers such as:
- [Variable replication factors](https://docs.gitlab.com/ee/administration/gitaly/index.html#replication-factor).
- [Strong consistency](https://docs.gitlab.com/ee/administration/gitaly/index.html#strong-consistency).
- [Distributed read capabilities](https://docs.gitlab.com/ee/administration/gitaly/index.html#distributed-reads).
We encourage customers currently using NFS for Git repositories to plan their migration by reviewing our documentation on [migrating to Gitaly Cluster](https://docs.gitlab.com/ee/administration/gitaly/index.html#migrate-to-gitaly-cluster).
---
deprecations:
- feature_name: "Release CLI be distributed as a generic package"
due: Dec 22, 2021
reporter: kbychu
description: |
The [release-cli](https://gitlab.com/gitlab-org/release-cli) will be released as a [generic package](https://gitlab.com/gitlab-org/release-cli/-/packages) starting in GitLab 14.2. We will continue to deploy it as a binary to S3 until GitLab 14.5 and stop distributing it in S3 in GitLab 14.6.
deprecations:
- feature_name: "Rename Task Runner pod to Toolbox"
due: October 22, 2021
reporter: dorrino
description: |
The Task Runner pod is used to execute periodic housekeeping tasks within the GitLab application and is often confused with the GitLab Runner. Thus, [Task Runner will be renamed to Toolbox](https://gitlab.com/groups/gitlab-org/charts/-/epics/25).
This will result in the rename of the sub-chart: `gitlab/task-runner` to `gitlab/toolbox`. Resulting pods will be named along the lines of `{{ .Release.Name }}-toolbox`, which will often be `gitlab-toolbox`. They will be locatable with the label `app=toolbox`.
---
deprecations:
- feature_name: Legacy database configuration
due: May 22, 2022
description: |
The syntax of [GitLabs database](https://docs.gitlab.com/omnibus/settings/database.html)
configuration located in `database.yml` is changing and the legacy format is deprecated. The legacy format
supported using a single PostgreSQL adapter, whereas the new format is changing to support multiple databases. The `main:` database needs to be defined as a first configuration item.
This deprecation mainly impacts users compiling GitLab from source because Omnibus will handle this configuration automatically.
- feature_name: Audit events for repository push events
due: May 22, 2022
description: |
Audit events for [repository events](https://docs.gitlab.com/ee/administration/audit_events.html#repository-push) are now deprecated and will be removed in GitLab 15.0.
These events have always been disabled by default and had to be manually enabled with a
feature flag. Enabling them can cause too many events to be generated which can
dramatically slow down GitLab instances. For this reason, they are being removed.
- feature_name: OmniAuth Kerberos gem
due: May 22, 2022
description: |
The `omniauth-kerberos` gem will be removed in our next major release, GitLab 15.0.
This gem has not been maintained and has very little usage. We therefore plan to remove support for this authentication method and recommend using the Kerberos [SPNEGO](https://en.wikipedia.org/wiki/SPNEGO) integration instead. You can follow the [upgrade instructions](https://docs.gitlab.com/ee/integration/kerberos.html#upgrading-from-password-based-to-ticket-based-kerberos-sign-ins) to upgrade from the `omniauth-kerberos` integration to the supported one.
Note that we are not deprecating the Kerberos SPNEGO integration, only the old password-based Kerberos integration.
- feature_name: GitLab Serverless
due: May 22, 2022
description: |
[GitLab Serverless](https://docs.gitlab.com/ee/user/project/clusters/serverless/) is a feature set to support Knative-based serverless development with automatic deployments and monitoring.
We decided to remove the GitLab Serverless features as they never really resonated with our users. Besides, given the continuous development of Kubernetes and Knative, our current implementations do not even work with recent versions.
......@@ -9,6 +9,5 @@ features:
categories:
- 'Cloud Native Installation'
description: |
- GitLab 14.3 is proud to announce the general availability of [the GitLab Operator](https://gitlab.com/gitlab-org/cloud-native/gitlab-operator/-/blob/master/README.md). The GitLab Operator allows users to deploy and run an instance of GitLab in an OpenShift or vanilla Kubernetes cluster. The GitLab Operator also automates day 2 operations such as upgrading components, application reconfiguration, and autoscaling. Check out the [GitLab Operator installation documentation](https://gitlab.com/gitlab-org/cloud-native/gitlab-operator/-/blob/master/doc/installation.md).
- We have removed the extra Ingress path for the Sidekiq administration panel, after [addressing the original need](https://gitlab.com/gitlab-org/charts/gitlab/-/issues/2731). This resolves several complications with external Ingress providers, such as Google's GCE and Amazon's ALB.
 
......@@ -4,7 +4,7 @@ features:
- name: "Audit events for changes to protected branch settings"
available_in: [premium, ultimate]
gitlab_com: true
image_url: '/images/unreleased/audit_events_protected_branches.png'
image_url: '/images/14_3/audit_events_protected_branches.png'
documentation_link: 'https://docs.gitlab.com/ee/administration/audit_events.html#project-events'
reporter: stkerr
stage: manage
......@@ -14,6 +14,7 @@ features:
description: |
GitLab now records additional audit events when changes are made to protected branches.
Specifically, events are now created when changes are made to:
- Who is allowed to push to the branch.
- Who is allowed to merge to the branch.
- Whether or not code owner approval is required.
......
......@@ -8,7 +8,7 @@ features:
stage: manage
categories:
- 'Audit Events'
image_url: '/images/unreleased/mr_settings_audit_events.png'
image_url: '/images/14_3/mr_settings_audit_events.png'
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/336211'
description: |
Audit events are now created if changes are made to the [merge request approval settings](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/settings.html)
......
......@@ -11,4 +11,4 @@ features:
- 'Value Stream Management'
issue_url: 'https://gitlab.com/gitlab-org/gitlab/-/issues/337256'
description: |
This change enables the DORA API-based Deployment Frequency API in group-level Value Stream Analytics for Premium customers. This can help you understand how often you are delivering increased value to your users. Also, higher deployment frequency means you are able to get feedback and iterate more quickly in delivering improvements and features.
This change enables the DORA API-based Deployment Frequency metric in group-level Value Stream Analytics for Premium customers. This can help you understand how often you are delivering increased value to your users. Also, higher deployment frequency means you are able to get feedback and iterate more quickly in delivering improvements and features.
......@@ -4,7 +4,7 @@ features:
- name: "GPG key displayed on a user's profile page"
available_in: [core, premium, ultimate]
documentation_link: 'https://docs.gitlab.com/ee/user/project/repository/gpg_signed_commits/#adding-a-gpg-key-to-your-account'
image_url: '/images/unreleased/gpg_key.png'
image_url: '/images/14_3/gpg_key.png'
reporter: hsutor
stage: manage
categories:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment