The chart-elasticsearch from samsung-cnct

Helm "delete" does not remove SA

Investigate why "helm delete" does not remove all artifacts created by the helm chart.

Elasticsearch curator

From @leahnp on August 1, 2017 22:40

In conjunction with: https://github.com/samsung-cnct/k2-charts/issues/63
Delete logs after 2 weeks

Copied from original issue: samsung-cnct/elasticsearch-kubernetes#8

Elasticsearch helm release in 1.6 fails (RBAC not enabled)

From @gdmello on October 5, 2017 20:35

Trying to setup an elasticsearch cluster, and it fails in a 1.6 with RBAC not enabled-

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.2", GitCommit:"477efc3cbe6a7effca06bd1452fa356e2201e1ee", GitTreeState:"clean", BuildDate:"2017-04-19T20:33:11Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.7+coreos.0", GitCommit:"c8c505ee26ac3ab4d1dff506c46bc5538bc66733", GitTreeState:"clean", BuildDate:"2017-07-06T17:38:33Z", GoVersion:"go1.7.6", Compiler:"gc", Platform:"linux/amd64"}

$ helm install --name elasticsearch --values values.yaml ../../k2-charts/elasticsearch --namespace=ft --debug
[debug] Created tunnel using local port: '54714'
[debug] SERVER: "localhost:54714"
[debug] Original chart version: ""
[debug] CHART PATH: /home/<username>/new_wk_spc/k2-charts/elasticsearch

Error: release elasticsearch failed: clusterroles.rbac.authorization.k8s.io "elasticsearch" is forbidden: attempt to grant extra privileges: [{[get] [] [services] [] []} {[get] [] [namespaces] [] []} {[get] [] [endpoints] [] []}] user=&{system:serviceaccount:kube-system:default 9789f564-a6b6-11e7-a6e0-5254007064d2 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]} ownerrules=[] ruleResolutionErrors=[]

Tiller shows no different error-

[tiller] 2017/10/05 19:02:26 preparing install for elasticsearch
[storage] 2017/10/05 19:02:26 getting release history for "elasticsearch"
[tiller] 2017/10/05 19:02:26 rendering elasticsearch chart using values
[tiller] 2017/10/05 19:02:26 performing install for elasticsearch
[tiller] 2017/10/05 19:02:26 executing 0 pre-install hooks for elasticsearch
[tiller] 2017/10/05 19:02:26 hooks complete for pre-install elasticsearch
[storage] 2017/10/05 19:02:26 getting release history for "elasticsearch"
[kube] 2017/10/05 19:02:26 building resources from manifest
[kube] 2017/10/05 19:02:26 creating 7 resource(s)
[tiller] 2017/10/05 19:02:26 warning: Release "elasticsearch" failed: clusterroles.rbac.authorization.k8s.io "elasticsearch" is forbidden: attempt to grant extra privileges: [{[get] [] [services] [] []} {[get] [] [namespaces] [] []} {[get] [] [endpoints] [] []}] user=&{system:serviceaccount:kube-system:default 9789f564-a6b6-11e7-a6e0-5254007064d2 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]} ownerrules=[] ruleResolutionErrors=[]
[storage] 2017/10/05 19:02:26 creating release "elasticsearch.v1"
[tiller] 2017/10/05 19:02:26 failed install perform step: release elasticsearch failed: clusterroles.rbac.authorization.k8s.io "elasticsearch" is forbidden: attempt to grant extra privileges: [{[get] [] [services] [] []} {[get] [] [namespaces] [] []} {[get] [] [endpoints] [] []}] user=&{system:serviceaccount:kube-system:default 9789f564-a6b6-11e7-a6e0-5254007064d2 [system:serviceaccounts system:serviceaccounts:kube-system system:authenticated] map[]} ownerrules=[] ruleResolutionErrors=[]

If I comment out the creation of the ClusterRole and ClusterRoleBinding, the deployment is successful. Looks like the conditional {{- if .Capabilities.APIVersions.Has "rbac.authorization.k8s.io/v1beta1"}} seems to trigger even if rbac is not enabled. I haven't looked into this conditional deeply, as the only other example of it's usage is in the prometheus operator.

Copied from original issue: samsung-cnct/k2-charts#135

Testing for elasticsearch

Set up tests for chart-elasticsearch.
This will involve researching unit tests for elasticsearch.
Here are some articles of possible interest (link is the final article of a three part series; the first two articles are linked in the first paragraph).

Create "logging-lite" ElasticSearch deployment

From @leahnp on August 1, 2017 23:17

Duplicate this repo as much as possible for maintainability.
Use a single statefulset to spinup a light weight single node data/master elasticsearch cluster
Use elastic curator to delete logs after 2 weeks.

Copied from original issue: samsung-cnct/elasticsearch-kubernetes#10

StorageClass Out of Date and Not Setable

This value:
volume.alpha.kubernetes.io/storage-class: anything
is deprecated and has been changed to:
volume.beta.kubernetes.io/storage-class: anything

Also, the value should be made configurable from the values.yaml. e.g.
volume.beta.kubernetes.io/storage-class: {{Values.storage_class}}

port chart-elasticsearch to gitlab

Follow instructions to create and editbuild/.gitlab-ci.yml from template
also create build/build.sh and build/test.sh according to instructions
make build.sh and test.sh executable
create secret variable in gitlab
add pipeline status badge to README
Remove the Jenkinsfile in the current repo.
When PR has merged, make sure that new image is being created on quay. Afterwards, please head back to the umbrella ticket and check off the chart-elasticsearch

samsung-cnct / chart-elasticsearch Goto Github PK

chart-elasticsearch's Introduction

Chart for Elasticsearch

Purpose

Architecture details

Kubernetes Resources

Installation

Curator

chart-elasticsearch's People

Contributors

Stargazers

Watchers

Forkers

chart-elasticsearch's Issues

Recommend Projects

Recommend Topics

Recommend Org