Skip to content

[v15] Fix major version check for stateless environment#54641

Closed
vapopov wants to merge 1 commit intobranch/v15from
vapopov/major-version-check-v15
Closed

[v15] Fix major version check for stateless environment#54641
vapopov wants to merge 1 commit intobranch/v15from
vapopov/major-version-check-v15

Conversation

@vapopov
Copy link
Copy Markdown
Contributor

@vapopov vapopov commented May 8, 2025

Backport #52837 to branch/v15

Changelog: Fixed major version check for stateless environment

* Added auth information resource with persisting teleport version

* Check the set of the auth info to compare with min/max versions in cluster

* Store only one entity for the cluster version

* Add CRUD endpoints
Change to use conditional update and retry
Fix spelling

* Add validation for version, sub kind, kind, name

* Rename to authinfo.go

* Assigning error after creating new resource

* Move retry logic to version check helper

* Call create/update depends on if resource is created already
Read local database once without retry

* Restrict major version downgrade

* Make `--skip-version-check` available for major upgrade check

* Fix linter warnings

* Add logs and make skip more safe in case of broke item in backend

* Remove deleting version item from process database, stateBackend doesn't support deletion (requires implementation for kube secrets storage)

* Rename AuthInfo to BackendInfo
Add cleanup of the version item from process storage after successful migration

* Make skip-version-check to upsert the version in backend

* Update lib/auth/version.go

Co-authored-by: Edoardo Spadolini <edoardo.spadolini@goteleport.com>

---------

Co-authored-by: Edoardo Spadolini <edoardo.spadolini@goteleport.com>
@vapopov vapopov force-pushed the vapopov/major-version-check-v15 branch from 01edb7f to 1f7fada Compare May 8, 2025 20:50
@vapopov vapopov closed this May 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants