![]() Please note that installation and debugging for Splunk Connect for Kubernetes through YAML is community-supported only. You can grab the manifest YAML files and use them to create the Kubernetes objects needed to deploy Splunk Connect for Kubernetes. Only deploying by Helm is supported by Splunk. To learn more about using and modifying charts, see: Helm install my-splunk-connect -f values.yaml splunk/splunk-connect-for-kubernetes To install and configure defaults with Helm: Helm is the only method that the Splunk software supports for installing Splunk Connect for Kubernetes. For more information on how to use and configure Helm Charts, see the Helm site and repository for tutorials and product documentation. Helm, maintained by the CNCF, allows the Kubernetes administrator to install, upgrade, and manage the applications running in their Kubernetes clusters. If you are installing the connector on Splunk Cloud, file a ticket with Splunk Customer Service and they will deploy the indexes for your environment, and generate your HEC token. Create a HEC token if you do not already have one.If you do not configure these indexes, Kubernetes Connect for Splunk uses the defaults created in your HTTP Event Collector (HEC) token. One events index, which will handle logs and objects (you may also create two separate indexes for logs and objects).Create a minimum of two Splunk platform indexes:.Perform the following steps before you install: Read the Prerequisites and Installation and Deployment documentation before you start your deployment of Splunk Connect for Kubernetes. Splunk Connect for Kubernetes supports installation using Helm. You can also create separate indexes for logs and objects, but you will need three Splunk platform indexes. One for both logs and Kubernetes objects, and one for metrics. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |