Repository navigation
Remove cloud-config from OSPs and OSM #436
Description
In-tree cloud providers have been disabled starting from k8s 1.29 hence we don't need to generate cloud-config for them.
{{ message }}
Remove
Activity
kubermatic-bot commentedon May 5, 2025
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with
/remove-lifecycle stale.If this issue is safe to close now please do so with
/close./lifecycle stale
buraksekili commentedon Jul 7, 2025
/assign
buraksekili commentedon Jul 10, 2025
This should be handled by #353.
Closing this in favour of #353
ahmedwaleedmalik commentedon Jul 10, 2025
The ticket is about "Remove cloud-config from OSPs and OSM" so removing the redundant code that's no longer required since k8s 1.29+ have in-tree providers disabled.
buraksekili commentedon Jul 11, 2025
Thank you @ahmedwaleedmalik for clarification!
I raised a PR based on your suggestions. I'd appreciate your reviews and thoughts there if you have availability. Thanks again!
ahmedwaleedmalik commentedon Jul 11, 2025
Sorry, i'm not actively working on OSM atm. 😔
kubermatic-bot commentedon Oct 9, 2025
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with
/remove-lifecycle stale.If this issue is safe to close now please do so with
/close./lifecycle stale
ahmedwaleedmalik commentedon Oct 10, 2025
/remove-lifecycle stale
4 remaining items
kubermatic-bot commentedon Apr 9, 2026
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with
/remove-lifecycle stale.If this issue is safe to close now please do so with
/close./lifecycle stale
kubermatic-bot commentedon May 9, 2026
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with
/remove-lifecycle rotten.Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with
/close./lifecycle rotten
kubermatic-bot commentedon Jun 8, 2026
Rotten issues close after 30d of inactivity.
Reopen the issue with
/reopen.Mark the issue as fresh with
/remove-lifecycle rotten./close
kubermatic-bot commentedon Jun 8, 2026
@kubermatic-bot: Closing this issue.
Details
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
kubermatic-bot commentedon Sep 7, 2026
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with
/remove-lifecycle stale.If this issue is safe to close now please do so with
/close./lifecycle stale
kubermatic-bot commentedon Oct 8, 2026
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with
/remove-lifecycle rotten.Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with
/close./lifecycle rotten