shivansh-gohem

Hi @francostellari @clubanderson, I'm studying KubeStellar's architecture and found this issue interesting. A few questions to understand the scope: 1. Should this be a new controller or extend an existing...

Thanks @francostellari! That's much clearer. So instead of a controller, you're thinking of using ArgoCD's declarative Secret-based registration where labeled Secrets are auto-discovered? A few questions to understand better: 1....

Hi @francostellari, I spent last night studying: - The current argocd/setup.yaml Job approach - PostCreateHook patterns (transport-controller, install-status-addon) - ArgoCD's declarative cluster registration docs I see the approach now: create...

Hi @MikeSpreitzer, I've carefully addressed all issues from the previous attempt (#3335): 1. ✅ All files are correctly saved and pushed to GitHub 2. ✅ All markdown syntax is valid...

Hi @MikeSpreitzer, Thank you for the detailed review. I've addressed all the issues you identified: ✅ Fixed Issues: Code fences (testing.md): All code blocks now have proper triple backtick fencing...

Hi @MikeSpreitzer could you please review!!!!1

Hi @francostellari @clubanderson, I need to clarify - while the PostCreateHook structure is in place and all CI checks pass, the implementation has TODO placeholders for the critical kubeconfig parsing...

Hi , @francostellari could you please guide further!!

Thanks a lot for the additional guidance, this clarifies the next steps for me. For cleanup on WDS deletion: I agree we shouldn’t leave the ArgoCD cluster registration behind. I’ll...

any updates @ngvanthanggit ?