-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A Fleet Server is required before enrolling agents with Fleet. #1
Comments
if you change the namespace, you need to make sure you also adjust the namespace name/connection between kibana and fleet server, see eck-ready-for-production/kibana.yaml Lines 17 to 18 in 1780545
if you are not using the default namespace anymore, you have to adjust the connection between the components with your new namespace name |
I have done this change already, I also made sure the namespace is added in the fleet, kibana and elasticsearch, and still nothing is comming up. For reference, I'm using the manifests:
fleet.yaml
|
After applying the manifest to my cluster, changing the namespace to an specific one (not
default
) for elasticsearch, kibana, fleet and heartbeat, I go into the kibana dashboard and click under Management --> Fleet, I get the following message:A Fleet Server is required before enrolling agents with Fleet.
. This is not the same behavour as yours in the video of this repository.Are there any configurations required besides applying the manifests?
My kubernetes version is 1.21, ECK installed via helm and stack installed via kubectl apply -f <>.yaml -n non-default-namespace,
This is what it is shown in the Fleet management view.
The text was updated successfully, but these errors were encountered: