Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Old tkr-source-controller needs to be removed when upgrading to (u)TKG 2.0 #3887

Closed
imikushin opened this issue Nov 10, 2022 · 0 comments · Fixed by #3900
Closed

Old tkr-source-controller needs to be removed when upgrading to (u)TKG 2.0 #3887

imikushin opened this issue Nov 10, 2022 · 0 comments · Fixed by #3900
Assignees
Labels
area/cc ClusterClass related area/tkr kind/bug PR/Issue related to a bug

Comments

@imikushin
Copy link
Contributor

Bug description

In TKG 1.6 and prior, tkr-source-controller is installed via a ClusterResourceSet (with ApplyOnce mode). TKG 2.0 introduces tkr-service with broader functionality, so the old tkr-source-controller needs to be removed.

Affected product area (please put an X in all that apply)

  • ( ) APIs
  • ( ) Addons
  • ( ) CLI
  • ( ) Docs
  • ( ) IAM
  • (X) Installation
  • ( ) Plugin
  • ( ) Security
  • ( ) Test and Release
  • ( ) User Experience
  • ( ) Developer Experience

Expected behavior

After upgrading from TKG 1.6 to uTKG, tkr-controller-manager deployment no longer exists in the tkr-system namespace.

Steps to reproduce the bug

  1. Upgrade from TKG 1.6 to uTKG.
  2. Notice that the tkr-controller-manager deployment still exists in the tkr-system namespace.

Version (include the SHA if the version is not obvious)

TKG 1.6

Environment where the bug was observed (cloud, OS, etc)

Relevant Debug Output (Logs, manifests, etc)

@imikushin imikushin added kind/bug PR/Issue related to a bug needs-triage Indicates an issue or PR needs to be triaged labels Nov 10, 2022
@imikushin imikushin self-assigned this Nov 10, 2022
@prkalle prkalle added area/tkr area/cc ClusterClass related and removed needs-triage Indicates an issue or PR needs to be triaged labels Nov 14, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
area/cc ClusterClass related area/tkr kind/bug PR/Issue related to a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants