Skip to content
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

Fleet agent never associates with kibana if basePath: /kibana is defined operator #8170

Open
dadez73 opened this issue Oct 31, 2024 · 0 comments
Labels

Comments

@dadez73
Copy link

dadez73 commented Oct 31, 2024

We are using ECK with Elastic Agents Managed by Fleet and have installed the Kubernetes Integration.

I noticed that if i rewrite the url basepath of kibana the operator still point to the default url that is without basepath. This block the fleet autonerollement , deployments that have kibanaRef: in config are not deployed as the operator cannot contact kibana.

Thank you!

Kibana config slice:

spec:
config:
monitoring:
kibana.collection.enabled: true
ui.ccs.enabled: false
server:
basePath: /kibana
host: 0.0.0.0
publicBaseUrl: https://XXXXXXX/kibana
rewriteBasePath: true

{"name":"eck-fleet-server","namespace":"elk"},"namespace":"elk","name":"eck-fleet-server","reconcileID":"f0cec043-f512-46b5-b0d6-f13f0b0b7299","error":"failed to request http://kibana-kb-http.elk.svc:5601/api/fleet/enrollment_api_keys?perPage=20&page=1, status is 404)

@botelastic botelastic bot added the triage label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant