Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detailed guide about migrating from karpenter namespace to kube-system namespace during 0.33.x upgrade #7598

Closed
kasvith opened this issue Jan 14, 2025 · 3 comments
Labels
documentation Improvements or additions to documentation lifecycle/closed lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage

Comments

@kasvith
Copy link

kasvith commented Jan 14, 2025

Description

Hi, we are early adopters of karpenter. While looking at the docs i saw that from v0.33.x the kube-system is recommended for karpenter installation including new CRDs with helm

But i could not find a detailed migration guide from an existing karpenter namespace to the kube-system. I saw there was a bullet point in v0.33 migration guide indicating that IRSA policy document need to be updated as well to ensure the functionality of the system. As per my understanding this is a very useful information hidden among lot of texts

I think these instructions are bit unclear and hard to follow, since our cluster is already in production doing changes like this without a detailed guide would cause more harm than good

would be nice to have some clear instruction of recommended namespace migration to the guides

How can the docs be improved?

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@kasvith kasvith added documentation Improvements or additions to documentation needs-triage Issues that need to be triaged labels Jan 14, 2025
@rschalo
Copy link
Contributor

rschalo commented Jan 30, 2025

Thanks for the feedback, did your team already proceed with the upgrade? To clarify, this was for upgrading from v0.32 to v0.33?

Was this part of a migration effort to v0.32+?

@rschalo rschalo added triage/needs-information Marks that the issue still needs more information to properly triage and removed needs-triage Issues that need to be triaged labels Jan 30, 2025
Copy link
Contributor

This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 28, 2025
@kasvith
Copy link
Author

kasvith commented Mar 3, 2025

hi @rschalo yes we managed to upgrade it

Yeah it was from 0.32 to 0.33.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation lifecycle/closed lifecycle/stale triage/needs-information Marks that the issue still needs more information to properly triage
Projects
None yet
Development

No branches or pull requests

2 participants