Can the Deployment Server also be a Deployment Client?

[jon_d_irish_ctr]

So I know that this sounds odd. Our Deployment Server is located on our Indexer Cluster Master. We are running all our Splunk systems on RHEL and I would like to deploy the Splunk App for Linux. According to the documentation, the App is only installed on the Search Heads. However, the Add-on needs to be installed on everything linux. That being said, how do you deploy to the Deployment server itself? I created /opt/splunk/etc/system/local/deploymentclient.conf on the Deployment Server and restarted Splunk, but it never shows up as a Deployment Client. Is the proper way to do this, manually installing Apps and Add-Ons on the Deployment Server?

Thanks,
Jon

[jotne]

Yes it can, but it may not be supported.  Tested on 9.0.1 and works fine.

Will try this in a large scale solution and come back with more experience.

Also mention here:
https://whatthesplunk.home.blog/2019/07/29/the-master-deployment-server/

Yes, the DS can send apps to itself. 

---

[gcusello]

Hi jon.d.irish.ctr,
I didn't think to this situation.
Anyway, if you run the command splunk set deploy-poll ip_deployment_server:8089 deploymentclient.conf file is updated but in Forwarder Management I cannot see the new forwarder.
So I think that it's not possible.
Bye.
Giuseppe

[skoelpin · Accepted solution]

No

Important: The deployment server cannot be a deployment client of itself. If it is, the following error will appear in splunkd.log: "This DC shares a Splunk instance with its DS: unsupported configuration". This has the potential to lead to situations where the deployment clients lose their ability to contact the deployment server.

http://docs.splunk.com/Documentation/Splunk/6.6.2/Updating/Configuredeploymentclients