Guidance on deploying the Splunk Enterprise Operator on Azure Kubernetes Service with automated reference implementation
Перейти к файлу
dwrightmsft b748480ca8
Merge pull request #1 from Azure/uidefinition
Added Custom UI Definition
2021-07-03 12:28:53 +01:00
scripts Removed blank line 2021-07-02 17:43:21 +01:00
.gitignore Initial commit of resources 2021-05-24 14:22:44 +01:00
CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md committed 2021-05-24 02:21:27 -07:00
LICENSE LICENSE committed 2021-05-24 02:21:28 -07:00
README.md Updated deploy link to main 2021-07-03 12:28:20 +01:00
SECURITY.md SECURITY.md committed 2021-05-24 02:21:29 -07:00
SUPPORT.md Initial commit of resources 2021-05-24 14:22:44 +01:00
azuredeploy.json Param casing 2021-07-03 11:48:10 +01:00
azuredeploy.portal.json Updated VM user parameter 2021-07-03 11:35:10 +01:00

README.md

Splunk Enterprise on Azure Kubernetes Service

This repo contains automation for deploying the Splunk Enterprise Operator for Kubernetes on AKS. This includes:

  • The deployment of a virtual network for the AKS cluster
  • The deployment of a storage account and container
  • The deployment of a private DNS zone
  • The deployment of a private storage endpoint in the cluster virtual network
  • The deployment of an AKS cluster across 3 Availability Zones
  • The deployment of the Splunk Operator for Kubernetes (with multi-site Indexer cluster) via Deployment Script
  • The deployment and configuration of the open source tool min.io to enable Splunk's SmartStore feature with Azure blob storage via Deployment Script
  • The deployment of App Gateway & Ingress Controller for access to Splunk UI
  • Disabling Transparent Huge Pages in line with Splunk best practices, using the AKS Custom Node Configuration feature

This repo is still in development, if you do find a bug or require an additional feature please do raise an issue or contribute by creating a pull request!

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.