Install fails with immediate error
See original GitHub issueChart version: elastic/logstash
Kubernetes version: 1.14
Kubernetes provider: E.g. GKE (Google Kubernetes Engine) AWS/EKS
Helm Version: 3.1.1
helm get release
output
Error: unable to build kubernetes objects from release manifest: error validating “”: error validating data: ValidationError(StatefulSet.spec): missing required field “serviceName” in io.k8s.api.apps.v1.StatefulSetSpec
Output of helm get release
Describe the bug: Installation fails Steps to reproduce:
1.helm install logstash elastic/logstash
Expected behavior: installation should succeed…
Provide logs and/or server output (if relevant):
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (1 by maintainers)
Top Results From Across the Web
How to troubleshoot Windows Installer errors - Microsoft Support
Right-click Windows Installer, and then click Properties. If the Startup type box is set to Disabled, change it to Manual. Click OK to...
Read more >Bug #1871268 “Installation fails due to useless immediate ...
Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected ; apt (Ubuntu). Fix Released. High.
Read more >If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >“Unable to install. A required install component is missing or ...
Unable to install A required install component is missing or corrupted. Error 3051" appears when attempting to install an Autodesk update.
Read more >Fix macOS “Installation failed, An error occurred while ...
Sometimes simply rebooting the Mac and trying again can resolve the failed installation error. Make sure the Mac is online and functionally ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Would it be possible to take a PR to support this before Helm 3 support becomes official, provided it doesn’t hamper Helm 2?
Hey, I think I’ve managed to fix this in the
values.yaml
file. At the bottom of the file, replacewith
Helm deploys the chart put the pod was stuck in a pending state for me, fixed it by adjusting the resources in values.