Open Stack

Sanjay,

When you run helm template without —validate flag, I don’t see StatefulSets being generated.That’s what you should be interested in.
Save that StatefulSet definition, verify it manually, and hopefully you would spot what is wrong there. Try to apply to your cluster.

Best regards,
Roman Gorshunov

> On 24 Apr 2020, at 15:53, Sanjay K <isanjayk5 at gmail.com> wrote:
> 
> Thank you for your reply. I forgot to mention that before deploying elasticsearch helm chart, I also deployed local-storage helm chart to create 3 PVs which might be used by elasticsearch chart. When I run helm template with debug and other parameters, it show below errors -
> 
> openstack-helm-infra/elasticsearch$ helm template elasticsearch local/elasticsearch --values values_overrides/local-storage.yaml -n openstack --validate --debug
> install.go:158: [debug] Original chart version: ""
> install.go:175: [debug] CHART PATH: /opt/stack/.cache/helm/repository/elasticsearch-0.1.0.tgz
> 
> Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(StatefulSet.spec): unknown field "strategy" in io.k8s.api.apps.v1.StatefulSetSpec
> ...
> However with below cmdline options, helm template generates the deployment info below without any issue..but actual helm install cmd fails to deploy the chart.
> 
> /openstack-helm-infra/elasticsearch$ helm template elasticsearch local/elasticsearch --values values_overrides/local-storage.yaml -n openstack --wait --debug  --dry-run
> install.go:158: [debug] Original chart version: ""
> install.go:175: [debug] CHART PATH: /opt/stack/.cache/helm/repository/elasticsearch-0.1.0.tgz
> 
> ---
> # Source: elasticsearch/templates/deployment-client.yaml
> apiVersion: v1
> kind: ServiceAccount
> metadata:
>   name: elasticsearch-elasticsearch-client
>   namespace: openstack
> ....
> ....
> 
> From the above, does it seem the issue is caused mismatch of tools version used in my k8s cluster and helm charts?
> I even tried with lesser version of k8s (v1.17), helm(v3.0.3) and docker(19.03.8) in my cluster, the issue is same with elasticsearch chart deploy.
> 
> thanks and regards,
> Sanjay
> 
> On Tue, Apr 21, 2020 at 6:13 PM Roman Gorshunov <paye600 at gmail.com> wrote:
> Hello Sanjay,
> 
> I have verified templates code for elasticsearch in
> openstack-helm-infra and relevant helm-toolkit code, and didn't find
> any visible problems. Deployments in Kubernetes v1.18 do support
> "strategy: ...".
> Could you try to render locally with "helm template ..." command and
> check the resulting deployments?
> 
> Best regards,
> Roman Gorshunov
> 
> On Tue, Apr 21, 2020 at 12:19 PM Sanjay K <isanjayk5 at gmail.com> wrote:
> >
> > Hi All,
> > Just forgot to mention my environment details if it throws any hints-
> > k8s - v1.18
> > helm - v3.1.2
> > openstack-helm-infra recent repo
> > docker - 19.03.7
> > VM OS- Ubuntu 16
> > openstack release - Stein
> >
> > thanks,
> > SanjayK
> >
> > On Mon, Apr 20, 2020 at 4:42 PM Sanjay K <isanjayk5 at gmail.com> wrote:
> >>
> >> Hello everyone,
> >> I have been trying to deploy elasticsearch helm chart in my k8s cluster consisting of 4 nodes (1 k8s master, 1 controller and 2 computes) after deploying fluentbit and fluentd helm charts which are deployed with success. I have plan to make the EFK (Elasticsearch-Fluentd-Kibana) stack running in my k8s cluster setup for logs management.
> >>
> >> However I face issues while deploying elasticsearch helm chart using the below command :
> >> $ helm install elasticsearch local/elasticsearch --values values_overrides/local-storage.yaml  -n openstack
> >> Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(StatefulSet.spec): unknown field "strategy" in io.k8s.api.apps.v1.StatefulSetSpec
> >>
> >> Can anyone point me if I missing anything?
> >> What are the prerequisites before deploying elasticsearch chart which intended to use local storage/pv in my case avoiding the default S3 storage as per the chart?
> >>
> >> Thanks for your pointers and suggestions.
> >> '
> >> best regards,
> >> SanjayK