I have been trying some other instructions from LLMs and google/medium topics I keep getting stuck at kibana not installing properly, I followed this video and was able to get the setup in first try, thanks Lian for such a great help
Lian, thanks for the nice explanation. One thing I found missing the security part to create users and roles. Actually I want to impersonate the users, roles, role mapping to test the access. In this it's missing, could you help in explaining how to plug this in this deployment? It would be really helpful for me.
The video has role detail: Kubernetes Security Role Based Access Control | Hands-on Demo using RBAC fix ELK Deployment Issue(th-cam.com/video/r05cPdoLoLw/w-d-xo.html). If you still have questions, please let me know.
Hi Lian, Thanks for your response. I am talking about users, roles, roles mapping as part of security feature inside ELK.. what I want to achieve.. use this helm3 deployment.. but want to create different test users, roles and permissions in ELK and test with their login. For example.. In ELK I login with dev_user where i have provided him readonly accesss.. as an devops admin want to ensure permissions are working as expected.. likewise for other users..business_user, dashboard_only user...etc
@Lian Now the thing is I am able to deploy successfully the ELK using helm3 but no login feature in elastic available.. its directly loading home or spaces.. I want login feature in elastic to enabled as part of this.. and want to create multiple user logins to test their roles and permissions in ELK
@@jdnielss how did you do below item? " Note that Kind < 0.7.0 are affected by a kind issue with mount points created from PVCs not writable by non-root users. kubernetes-sigs/kind#1157 fix it in Kind 0.7.0. The workaround for Kind < 0.7.0 is to install manually Rancher Local Path Provisioner and use local-path storage class for Elasticsearch volumes (see Makefile instructions). Usage For Kind >= 0.7.0: Deploy Elasticsearch chart with the default values: make install For Kind < 0.7.0: Deploy Elasticsearch chart with local-path storage class: make install-local-path"
@@TechwithLian i installed using helm3 from github, and get error Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" ) Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
Im getting "Error: INSTALLATION FAILED: template: elasticsearch/templates/statefulset.yaml:303:27: executing "elasticsearch/templates/statefulset.yaml" at : can't evaluate field master in type interface {}"
I have been trying some other instructions from LLMs and google/medium topics I keep getting stuck at kibana not installing properly, I followed this video and was able to get the setup in first try, thanks Lian for such a great help
This tutorial saved me hours of searching
Great! It works.
Hello professor, i cant access kibama, cause i dont have the user and pass. How can i get it!!
did you use imageTag=7.15.0?
Lian, thanks for the nice explanation. One thing I found missing the security part to create users and roles.
Actually I want to impersonate the users, roles, role mapping to test the access. In this it's missing, could you help in explaining how to plug this in this deployment? It would be really helpful for me.
The video has role detail: Kubernetes Security Role Based Access Control | Hands-on Demo using RBAC fix ELK Deployment Issue(th-cam.com/video/r05cPdoLoLw/w-d-xo.html). If you still have questions, please let me know.
and Role-based Access Control(helm.sh/docs/topics/rbac/)
For example, run helm create RBACTest , and change serviceAccount of values.yaml, next change serviceaccount.yaml in templates folder
Hi Lian, Thanks for your response.
I am talking about users, roles, roles mapping as part of security feature inside ELK.. what I want to achieve.. use this helm3 deployment.. but want to create different test users, roles and permissions in ELK and test with their login.
For example.. In ELK I login with dev_user where i have provided him readonly accesss.. as an devops admin want to ensure permissions are working as expected.. likewise for other users..business_user, dashboard_only user...etc
@Lian Now the thing is I am able to deploy successfully the ELK using helm3 but no login feature in elastic available.. its directly loading home or spaces.. I want login feature in elastic to enabled as part of this.. and want to create multiple user logins to test their roles and permissions in ELK
In kibana 8.00 version Index patterns has been renamed to data views
Good to know! Thanks
I'll plan to upgrade the video.
upgrade it pls
@@TechwithLian
0/1 nodes are available: 1 node(s) didn't find available persistent volumes to bind.
Could share your ENV detail? did you enable default-storageclass and storage-provisioner in Minikube?
@@TechwithLian i use AWS EKS, i download values from kubernetes-kind
@@jdnielss how did you do below item?
"
Note that Kind < 0.7.0 are affected by a kind issue with mount points created from PVCs not writable by non-root users. kubernetes-sigs/kind#1157 fix it in Kind 0.7.0.
The workaround for Kind < 0.7.0 is to install manually Rancher Local Path Provisioner and use local-path storage class for Elasticsearch volumes (see Makefile instructions).
Usage
For Kind >= 0.7.0: Deploy Elasticsearch chart with the default values: make install
For Kind < 0.7.0: Deploy Elasticsearch chart with local-path storage class: make install-local-path"
ohh, do you have a video tutorial? I'm confused
@@TechwithLian i installed using helm3 from github, and get error Readiness probe failed: Waiting for elasticsearch cluster to become ready (request params: "wait_for_status=green&timeout=1s" )
Cluster is not yet ready (request params: "wait_for_status=green&timeout=1s" )
All, please add --set imageTag=7.15.0 in "helm install elasticsearch" command
Im getting
"Error: INSTALLATION FAILED: template: elasticsearch/templates/statefulset.yaml:303:27: executing "elasticsearch/templates/statefulset.yaml" at : can't evaluate field master in type interface {}"
please try to add the below item into values.yaml.
roles:
master: "true"
@@TechwithLian Hey thanks for the reply! I will try, many thanks Lian!