search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.67k stars 8.23k forks source link

Include NGINX Ingress Controller package in custom Kubernetes integration onboarding process #150291

Open MichaelKatsoulis opened 1 year ago

MichaelKatsoulis commented 1 year ago

Currently, while adding a new agent, in case the user has selected a policy that includes Kubernetes integration the process is customised.

The correct kubernetes manifest is presented and the user can download it or copy and then apply it. In case kubernetes integration is not part of the policy, the normal process continues with the policy file being presented instead of the k8s manifest.

For standalone agent due to https://github.com/elastic/kibana/issues/136014 , in case no kubernetes integration is part of the policy, the users does not even have the option to choose kubernetes as a platform.

There is a package(maybe there are more like KSPM) that should be also considered as one that is meaningful only inside a kubernetes cluster and would need the Kubernetes manifest to be provided in both managed and standalone agent.

This is the new NGINX Ingress Controller package. NGINX Ingress Controller is an application that runs in a k8s cluster and configures an HTTP load balancer according to Ingress resources.

In case a user has selected this integration and want to use standalone agent they don't have the option to get the manifest. Also in case of managed agent addition, kubernetes platform is not the default one selected.

ChrsMark commented 1 year ago

I guess that the package will only be enabled if ingress Pods exist in the cluster, right? I think the condition that the package relies on will do the trick. Could you confirm this?

We just don't want to enable a scraper that would get errors and fill ES with these.