What, if anything, is the expected effect on an installed, registered, and running Harness Delegate, type Kubernetes, of someone removing, via the Harness Manager, the organization or project with which the delegate is associated?
Response from @Usheer_Fotedar at Harness Support:
Thank you for reaching out to Harness Support.
As delegates run your your infrastructure and connect to harness manager. Once you remove/delete the associated project/org. The delegate will still be running on your infra and you will need to stop/delete it from there.
Let us know if you have any further questions.
Also mentioning in general as this ticket channel is dedicated Harness Support
channel , let’s track this here itself instead of the community post.
I am left to wonder what, if any, effect the removal of an associated organization or project is expected to have on the running Harness Delegate.
I have found through experimentation that a delegate will fail to register if the project with which it is to be associated does not exist.
@Usheer_Fotedar, would you please clarify? Are you telling us that the delegate is expected in either situation to continue to run, without logging any sort of error or warning, apparently operating functionally as before, even when it is associated with a nonexistent organization or project, so long as the org or project existed at the time of registration?
Please note that the Harness support team is not supporting the Harness community. Our focus and mandate are paying customers, that are under agreement and NDA with Harness. We have a separate team that is focused on the Harness community as it is a combination of paying customers, prospects, and users of our source available product. Due to this distinction, the Harness support team is not directly engaged in the Harness community. You are welcome to post in our community and contribute to it, but you should not expect the support team to engage with you there. Accordingly, you should not expect a follow-up when you tag support team members in the community.
As for the question you asked in the community, we don’t yet know the answer, and we are working to get it.
Senior Director, Customer Success Engineering
We have Three different scopes (Account, Organisation, and Project level) in our NextGen. When you create any connector or delegate at the respective level then they are accessible to the scope associated with it you can find more info on this here: Add and Manage Resource Groups - HelpDocs
When you have spun up any delegate at the Organisation or Project level and you were making use of the same in Harness for different tasks and when you removed associated Project or Organisation then the delegate which was created that project or Organisation scope will not exist in Harness but it will still available and it will be in Running state in your Kubernetes cluster.
The delegate will still be running on your infra and you will need to stop/delete it from there. Please let us know if this helps and did we answer your queries?
Nandeesh G K
Why would I need to delete the running delegate?
My understanding of what you stated is that no effect is expected. A running and registered delegate associated with a nonexistent organization or project will continue to run without indication of failure unless and until it is stopped. Correct?
Yes your understanding is correct no effect is expected. A running and registered delegate associated with a nonexistent organization or project will continue to run without indication of failure unless and until it is stopped.
You dont need to delete the running delegate mandatorily its upto user convince.