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
Until version 7.14.0 and ECK version 2.10.0, Elastic Agent in Fleet mode has to run as root and in the same namespace as the Elasticsearch cluster it connects to.
It is not possible to run Agent as non root and in a namespace other than the one where Elasticsearch is deployed. This check is preventing this kind of setup to be deployed:
funcapplyRelatedEsAssoc(agent agentv1alpha1.Agent, esAssociation commonv1.Association, builder*defaults.PodTemplateBuilder) (*defaults.PodTemplateBuilder, error) {
ifesAssociation==nil {
returnbuilder, nil
}
esRef:=esAssociation.AssociationRef()
if!esRef.IsExternal() &&!agent.Spec.FleetServerEnabled&&agent.Namespace!=esRef.Namespace {
// check agent and ES share the same namespacereturnnil, fmt.Errorf(
"agent namespace %s is different than referenced Elasticsearch namespace %s, this is not supported yet",
agent.Namespace,
esAssociation.AssociationRef().Namespace,
)
}
We should understand if it safe to remove this check and fix the documentation.
Despite what the documentation suggests:
It is not possible to run Agent as non root and in a namespace other than the one where Elasticsearch is deployed. This check is preventing this kind of setup to be deployed:
We should understand if it safe to remove this check and fix the documentation.
It might be an oversight of #6700
The text was updated successfully, but these errors were encountered: