You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 17, 2024. It is now read-only.
Let's use a BDD approach to validate the official Helm charts for elastic. Something like this:
@helm@k8s@metricbeatFeature: The Helm chart is following product recommended configuration for KubernetesScenario: The Metricbeat chart will create recommended K8S resourcesGiven a cluster is running
When the "metricbeat" Elastic's helm chart is installed
Then a pod will be deployed on each node of the cluster by a DaemonSet
And a "Deployment" will manage additional pods for metricsets querying internal services
And a "kube-state-metrics" chart will retrieve specific Kubernetes metrics
And a "ConfigMap" resource contains the "metricbeat.yml" content
And a "ConfigMap" resource contains the "kube-state-metrics-metricbeat.yml" content
And a "ServiceAccount" resource manages RBAC
And a "ClusterRole" resource manages RBAC
And a "ClusterRoleBinding" resource manages RBAC
Let's use a BDD approach to validate the official Helm charts for elastic. Something like this: