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
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.
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)
The text was updated successfully, but these errors were encountered: