marcusschiesser.de

What It Is

Marcus Schiesser’s site is closer to a personal technical blog than a standalone SaaS product or a traditional developer tool. The crawled content shows that the author positions himself as a Splunk and Kubernetes Specialist, with articles focused on configuring Splunk on Kubernetes, Secret management, GitOps templates, and cloud-native infrastructure practices involving EKS, Terraform, EFS, and related tools.

Core Capabilities and Technical Scope

In terms of “features and use cases,” its value mainly lies in documenting real-world engineering workarounds. For example, while the Splunk K8S Operator recommends packaging .conf files via Splunk apps, certain configurations—such as adding new users—cannot be completed through an app. The article proposes approaches such as manual configuration or deploying a second K8S instance for configuration purposes, and provides YAML examples. Other posts discuss replication strategies when Kubernetes does not allow Secrets to be shared across namespaces, as well as ways to work around Splunk Operator limitations when it cannot inject passwords from K8S Secrets, using full configuration-file Secrets and Bash templating scripts instead.

The supported technology stack is fairly clear, including Kubernetes, Splunk Operator, Splunk Docker images, GitOps, GitHub, Terraform, AWS EKS, EFS CSI Driver, and Bash. At the API/SDK level, the site itself does not provide API or SDK information; it is more about configuring and integrating existing cloud-native toolchains.

Pricing and Open-Source Status

The crawled text does not show any pricing, subscription, or commercial support information, so it can only be considered freely readable technical content. The articles mention a splunk-gitops GitHub template, but no license is provided, so its open-source licensing status cannot be determined from this alone. As for self-hosting, much of the content focuses on self-managed Splunk on Kubernetes and EKS clusters, but the website itself is not a deployable product.

Pros, Cons, and Best-Fit Users

Its strengths are that the problems are specific and the guidance is highly practical. It is suitable for platform engineers, DevOps engineers, and SREs who are already running Splunk on Kubernetes, want to bring configuration under GitOps, or need to handle Secret and persistent volume issues. The drawbacks are that the scope is narrow and assumes readers already have a foundation in Splunk, K8S, and Terraform. The site is not systematic documentation, and it lacks a version compatibility matrix, support channels, and a complete end-to-end tutorial structure.

Access from China and Alternatives

Access from mainland China is not reflected in the crawled text, so it is marked as unknown. If access is unstable, users may want to prioritize the Splunk official documentation, Splunk Operator GitHub, Kubernetes official documentation, Terraform AWS Provider documentation, and AWS EKS/EFS CSI Driver documentation. Overall, it is best used as an experience-based supplement for solving specific Splunk on K8S issues, rather than as the sole authoritative source.