Vitess Operator v2.10.0

What's Changed

• Fix versions and tests by @GuptaManan100 in #378
• Update Release Instructions by @GuptaManan100 in #380
• Upgrade Vitess Dependency to Latest by @github-actions in #381
• Upgrade Vitess Dependency to Latest by @github-actions in #384
• build(deps): Bump golang.org/x/net from 0.5.0 to 0.7.0 by @dependabot in #385
• Fix mysqld image key for mysql 80 images by @GuptaManan100 in #386
• Upgrade Vitess Dependency to Latest by @github-actions in #388
• Update main tests after release of v2.9.0 by @GuptaManan100 in #390
• Improve release instructions and script after the 2.9.0 release by @frouioui in #391
• Pin Docker image version in Buildkite by @GuptaManan100 in #398
• Update PodDisruptionBudget to policy/v1 by @jcarrig in #397
• Add support for container lifecycle hooks in VTGate by @stankevich in #406
• Remove unwanted file runrunrun.sh by @frouioui in #407
• [VTAdmin] Change vars from REACT_APP to VITE by @notfelineit in #404
• Upgrade Vitess Dependency to Latest + Go version to 1.20.2 by @github-actions in #408
• Upgrade Vitess Dependency to Latest by @github-actions in #414
• Upgrade Vitess Dependency to Latest by @github-actions in #415
• Upgrade Vitess Dependency to Latest by @github-actions in #418
• Upgrade Vitess Dependency to Latest by @github-actions in #419
• Complete the Reshard before deleting the shard by @GuptaManan100 in #420
• Upgrade Vitess Dependency to Latest by @github-actions in #424
• build(deps): Bump github.com/docker/distribution from 2.8.1+incompatible to 2.8.2+incompatible by @dependabot in #423
• Upgrade Vitess Dependency to Latest by @github-actions in #425
• Upgrade Vitess Dependency to Latest by @github-actions in #427
• New release 2.10.0-rc1 by @mattlord in #429

New Contributors

• @stankevich made their first contribution in #406
• @notfelineit made their first contribution in #404

Full Changelog: v2.9.2...v2.10.0

Vitess Operator v2.10.0-rc1

What's Changed

• Release PR for 2.9.0-rc1 by @GuptaManan100 in #377
• Fix versions and tests by @GuptaManan100 in #378
• Update Release Instructions by @GuptaManan100 in #380
• Upgrade Vitess Dependency to Latest by @github-actions in #381
• Upgrade Vitess Dependency to Latest by @github-actions in #384
• build(deps): Bump golang.org/x/net from 0.5.0 to 0.7.0 by @dependabot in #385
• Fix mysqld image key for mysql 80 images by @GuptaManan100 in #386
• Upgrade Vitess Dependency to Latest by @github-actions in #388
• Update main tests after release of v2.9.0 by @GuptaManan100 in #390
• Improve release instructions and script after the 2.9.0 release by @frouioui in #391
• Pin Docker image version in Buildkite by @GuptaManan100 in #398
• Update PodDisruptionBudget to policy/v1 by @jcarrig in #397
• Add support for container lifecycle hooks in VTGate by @stankevich in #406
• Remove unwanted file runrunrun.sh by @frouioui in #407
• [VTAdmin] Change vars from REACT_APP to VITE by @notfelineit in #404
• Upgrade Vitess Dependency to Latest + Go version to 1.20.2 by @github-actions in #408
• Upgrade Vitess Dependency to Latest by @github-actions in #414
• Upgrade Vitess Dependency to Latest by @github-actions in #415
• Upgrade Vitess Dependency to Latest by @github-actions in #418
• Upgrade Vitess Dependency to Latest by @github-actions in #419
• Complete the Reshard before deleting the shard by @GuptaManan100 in #420
• Upgrade Vitess Dependency to Latest by @github-actions in #424
• build(deps): Bump github.com/docker/distribution from 2.8.1+incompatible to 2.8.2+incompatible by @dependabot in #423
• Upgrade Vitess Dependency to Latest by @github-actions in #425
• Upgrade Vitess Dependency to Latest by @github-actions in #427

New Contributors

• @dependabot made their first contribution in #385
• @stankevich made their first contribution in #406
• @notfelineit made their first contribution in #404

Full Changelog: v2.9.0-rc1...v2.10.0-rc1

Vitess Operator v2.9.2

What's Changed

• [release-2.9] Update PodDisruptionBudget to policy/v1 by @jcarrig in #413

Full Changelog: v2.9.1...v2.9.2

Vitess Operator v2.8.4

What's Changed

• [release-2.8] Update PodDisruptionBudget to policy/v1 by @jcarrig in #412

Full Changelog: v2.8.3...v2.8.4

Vitess Operator v2.7.5

What's Changed

• [release-2.7] Update PodDisruptionBudget to policy/v1 by @jcarrig in #411

Full Changelog: v2.7.4...v2.7.5

Vitess Operator v2.9.1

What's Changed

• Release of vtop 2.9 by @GuptaManan100 in #389

Full Changelog: v2.9.0...v2.9.1

Vitess Operator v2.8.3

What's Changed

• [release-2.8] Fix rbac file in tests (#352) by @vitess-bot in #353
• Release v2.8.2 by @frouioui in #348
• [release-2.8] Fix operator image in operator.yaml by @GuptaManan100 in #374

Full Changelog: v2.8.2...v2.8.3

Vitess Operator v2.7.4

What's Changed

• Update version to 2.7.4 by @GuptaManan100 in #307
• [release-2.7] Update the release instructions (#315) by @vitess-bot in #316
• [release-2.7] Fix operator image in operator.yaml by @GuptaManan100 in #375

Full Changelog: v2.7.3...v2.7.4

Vitess Operator v2.9.0

Major Changes

EnforceSemiSync Removal

The config enforceSemiSync is removed from the VitessReplicationSpec. This configuration is no longer requied.
If the users want to configure semi-sync replication, they should set the durabilityPolicy config to semi_sync in the keyspace specification.
This change of not using enforceSemiSync should be done before upgrading to 2.9.0 version of the operator otherwise the configuration would not be accepted.

VTOrc becomes mandatory

VTOrc is now a required component of Vitess starting from v16. So, the vitess-operator will always run
a VTOrc instance for a keyspace, even if its configuration is unspecified.

MySQL Upgrade Path

With the latest version of Vitess (v16.0.0) the default MySQL version changed from 5.7 to 8.0.30.
Meaning that the vitess/lite:v15.0.2 and vitess/lite:v16.0.0 are running different MySQL major version.
If you want to remain on MySQL 5.7, we invite you to use vitess/lite:v16.0.0-mysql57.

Otherwise, if you were already running MySQL 8.0, with for instance vitess/lite:v15.0.2-mysql80, note that here the patch version of MySQL will also change between v15 and v16.
In v16.0.0 we are bumping the patch version of MySQL 80 from 8.0.23 to 8.0.30.
In order for you to correctly upgrade, there is a certain path to follow:

1. Add innodb_fast_shutdown=0 to your extra cnf in your YAML file.
2. Apply this file.
3. Wait for all the pods to be healthy.
4. Then change your YAML file to use the new Docker Images (vitess/lite:v16.0.0, defaults to mysql80).
5. Remove innodb_fast_shutdown=0 from your extra cnf in your YAML file.
6. Apply this file.

What's Changed

• Change version to 2.8.0 after release by @GuptaManan100 in #275
• Reduce Vtadmin test flakiness by @GuptaManan100 in #278
• VTAdmin cluster-config cleanup by @GuptaManan100 in #279
• Upgrade Vitess dependency to 14.0.0 by @GuptaManan100 in #280
• Remove removed flag in vttablet by @GuptaManan100 in #281
• Introduce Durability Policy in VTop by @GuptaManan100 in #282
• Augment VTAdmin test to also test VTOrc setup by @GuptaManan100 in #283
• pkg/apis/planetscale/v2: fix VitessKeyRange rounding logic by @mdlayher in #268
• Fix: init_db.sql file to be in sync with main on Vitess by @GuptaManan100 in #293
• Dependency upgrade for go and Vitess and CI rules fix by @GuptaManan100 in #296
• Remove Deprecated flags from VTop by @GuptaManan100 in #300
• VTop corresponding changes for VTAdmin docker image changes to use Nginx by @GuptaManan100 in #304
• Addition of the release automation script by @frouioui in #308
• Update the release instructions by @frouioui in #315
• Upgrade Vitess Dependency and add a cron for it by @GuptaManan100 in #313
• Fix Vitess Upgrade Workflow to also run go mod tidy by @GuptaManan100 in #318
• Upgrade Vitess Dependency to Latest by @github-actions in #319
• Upgrade Vitess Dependency to Latest by @github-actions in #320
• Addition of a comment in the upgrade vitess deps workflow by @frouioui in #322
• VTOrc Deployment fix and miscellaneous changes. by @GuptaManan100 in #324
• Upgrade test to expect the latest image to be of version 16 by @GuptaManan100 in #333
• Upgrade Vitess Dependency to Latest by @github-actions in #329
• Update k8s compatibility table and increase memory limit by @frouioui in #334
• Update the release script and documentation with more verbose by @frouioui in #331
• Upgrade Vitess Dependency to Latest by @github-actions in #336
• Upgrade the AWS and GCP quickstarts along with the API doc by @frouioui in #323
• Upgrade Vitess Dependency to Latest by @github-actions in #340
• Upgrade Vitess Dependency to Latest by @github-actions in #343
• Upgrade Vitess Dependency to Latest by @github-actions in #344
• Upgrade Vitess Dependency to Latest by @github-actions in #346
• Upgrade Vitess Dependency to Latest by @github-actions in #349
• Upgrade Vitess Dependency to Latest by @github-actions in #350
• Upgrade Vitess Dependency to Latest by @github-actions in #351
• Fix rbac file in tests by @GuptaManan100 in #352
• Upgrade Vitess Dependency to Latest by @github-actions in #355
• Fix vtctld deployment to allow ListBackups to work by @GuptaManan100 in #356
• Remove removed flags in vtctld by @GuptaManan100 in #360
• Upgrade Vitess Dependency to Latest by @github-actions in #359
• Bug: Fix vtadmin resources by @nianfei97 in #358
• Operator changes to remove enable_semi_sync by @GuptaManan100 in #364
• Remove enable_realtime_stats flag since it is removed by @GuptaManan100 in #366
• Upgrade Vitess Dependency to Latest by @github-actions in #367
• Makes VTOrc mandatory by @GuptaManan100 in #368
• Set vttablet init container resource requests and limits by @GuptaManan100 in #370
• Support upgrade of minor MySQL version by @frouioui in #361
• Update the release instructions after v16 code freeze by @frouioui in #373
• Add release notes regarding MySQL upgrade path in v16.0.0 by @frouioui in #376
• Document the version upgrade of the tests in the docs by @frouioui in #357
• Update Go dependency, compatibility table, Vitess dependency and fix upgrades by @GuptaManan100 in #371
• Release PR for 2.9.0-rc1 by @GuptaManan100 in #377
• Fix tests in release-2.9 by @GuptaManan100 in #379
• [release-2.9] Fix mysqld image key for mysql 80 images by @GuptaManan100 in #387

New Contributors

• @mdlayher made their first contribution in #268
• @nianfei97 made their first contribution in #358

Full Changelog: v2.7.1...v2.9.0

Vitess Operator v2.9.0-rc1

Summary

Recommended for use with Vitess v16.0.0-rc1

Major Changes

EnforceSemiSync Removal

The config enforceSemiSync is removed from the VitessReplicationSpec. This configuration is no longer requied.
If the users want to configure semi-sync replication, they should set the durabilityPolicy config to semi_sync in the keyspace specification.
This change of not using enforceSemiSync should be done before upgrading to 2.9.0 version of the operator otherwise the configuration would not be accepted.

VTOrc becomes mandatory

VTOrc is now a required component of Vitess starting from v16. So, the vitess-operator will always run
a VTOrc instance for a keyspace, even if its configuration is unspecified.

MySQL Upgrade Path

With the latest version of Vitess (v16.0.0) the default MySQL version changed from 5.7 to 8.0.30.
Meaning that the vitess/lite:v15.0.2 and vitess/lite:v16.0.0 are running different MySQL major version.
If you want to remain on MySQL 5.7, we invite you to use vitess/lite:v16.0.0-mysql57.

Otherwise, if you were already running MySQL 8.0, with for instance vitess/lite:v15.0.2-mysql80, note that here the patch version of MySQL will also change between v15 and v16.
In v16.0.0 we are bumping the patch version of MySQL 80 from 8.0.23 to 8.0.30.
In order for you to correctly upgrade, there is a certain path to follow:

1. Add innodb_fast_shutdown=0 to your extra cnf in your YAML file.
2. Apply this file.
3. Wait for all the pods to be healthy.
4. Then change your YAML file to use the new Docker Images (vitess/lite:v16.0.0, defaults to mysql80).
5. Remove innodb_fast_shutdown=0 from your extra cnf in your YAML file.
6. Apply this file.