GitLab

Upgrade `gprd-gitlab-gke` node pools batch 4

See merge request !2230

The following node-pools will be upgraded

* default-1

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

Create console node for PoC 12011

See merge request !2229

https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12011

Upgrade `gprd-gitlab-gke` node pools batch 3

See merge request !2227

Bump the machine type for web node in `pre`

See merge request !2228

We have been receiving a few alerts about blackbox probes for `pre`
failing (the only thing in `pre` we monitor). We will up the machine
size for this node to alleviate any resource contention.

https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11991

The following node-pools will be upgraded

* catchall-0

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

Upgrade `gprd-gitlab-gke` node pools batch 2

See merge request !2224

Bump storge-buckets module

See merge request !2223

The following node-pools will be upgraded

* sidekiq-urgent-other-1
* sidekiq-low-urgency-cpu-bound-1
* sidekiq-urgent-cpu-bound-1

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

Upgrade `gprd-gitlab-gke` node pools batch 1

See merge request !2222

Upgrade `gprd-gitlab-gke` masters only to 1.17.13-gke.1400

See merge request !2221

Bump storage-buckets to include new Prometheus retention[0].

Tweak bump-module to "fully match" module name to avoid bumping
similarly named modules (i.e. ci-storage-buckets vs sotrage-buckets)

[0]: https://ops.gitlab.net/gitlab-com/gl-infra/terraform-modules/google/storage-buckets/-/merge_requests/36

https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3064Signed-off-by: Ben Kochie <[email protected]>

The following node-pools will be upgraded

* shell-1
* git-https-1
* registry-0
* sidekiq-memory-bound-2

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

Part of
* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

Explicitly pin versions of `gprd-gitlab-gke` masters and nodes

See merge request !2220

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3072
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

As a pre-requisite to upgrading the `gprd-gitlab-gke` Kubernetes
cluster, we want to explicitly pin the versions in terraform so that
we can slowly upgrade masters and node pools one at a time, independantly
of each other.

Revert "Enable GKE auto upgrades on nodes in gke-us-east1-d"

See merge request !2219

This reverts commit 449a5fe8.

Part of https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3038

Upgrade gke masters to 1.17 in `gke-us-east1-d`

See merge request !2216

Enable GKE auto upgrades on nodes in gke-us-east1-d

See merge request !2215

Updated gitlab-services IP

See merge request !2218

Update to terraform version 0.12.29

See merge request !2214

Adds node pools for registry in staging

See merge request !2217

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3023
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

This will force the GKE masters for cluster `gke-us-east1-d` to
upgrade to to 1.17 but not the node pools.

Following instructions at

https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/uncategorized/k8s-cluster-upgrade.md#step-2

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3023

* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

This will enable GKE auto upgrades on the nodes only for `gke-us-east1-b`.
As the nodes will never auto upgrade beyond the masters, enabling this
simply allows us to upgrade the masters with another MR without also
forcing the node pools to all upgrade at the exact same time.

Following documentation at

https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/uncategorized/k8s-cluster-upgrade.md#step-1

This prepares the ground for the v0.13 upgrade. See
https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11921

Revert "Enable GKE auto upgrades on nodes in gke-us-east1-c"

See merge request !2213

This reverts commit b1ff76cd.

Part of https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3038

Upgrade gke masters to 1.17 in `gke-us-east1-c`

See merge request !2210

Enable GKE auto upgrades on nodes in gke-us-east1-c

See merge request !2209

Creates a node pool in the zonal clusters for registry

See merge request !2211

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3023
* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

This will force the GKE masters for cluster `gke-us-east1-c` to
upgrade to to 1.17 but not the node pools.

Following instructions at

https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/uncategorized/k8s-cluster-upgrade.md#step-2

Part of

* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3023

* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796

This will enable GKE auto upgrades on the nodes only for `gke-us-east1-c`.
As the nodes will never auto upgrade beyond the masters, enabling this
simply allows us to upgrade the masters with another MR without also
forcing the node pools to all upgrade at the exact same time.

Following documentation at

https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/uncategorized/k8s-cluster-upgrade.md#step-1

Revert "Enable GKE auto upgrades on nodes in gke-us-east1-b"

See merge request !2208

This reverts commit cb422f3d.

Part of

* https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/11796
* https://gitlab.com/gitlab-com/gl-infra/production/-/issues/3023