Document limitation on Minikube without CNI #6075
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fleet Server initialization fails on minikube when CNI is disabled
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
thbkrkr
reviewed
Oct 14, 2022
| @@ -532,6 +532,11 @@ To establish trust, the Pod needs to update the CA store through a call to `upda | |||
| === Running Endpoint Security integration | |||
| Running Endpoint Security link:https://www.elastic.co/guide/en/security/current/install-endpoint.html[integration] is not yet supported in containerized environments, like Kubernetes. This is not an ECK limitation, but the limitation of the integration itself. Note that you can use ECK to deploy Elasticsearch, Kibana and Fleet Server, and add Endpoint Security integration to your policies if Elastic Agents running those policies are deployed in non-containerized environments. | |||
|
|
|||
| === Fleet Server initialization fails on minikube when CNI is disabled | |||
| When deployed with ECK, the Fleet Server pod makes an http call to itself during fleet initialization using its service endpoint. Since a link:https://github.com/kubernetes/minikube/issues/1568[pod cannot reach itself through its service on minikube] when CNI is disabled, the call hangs until the connection times out and the pod goes into a crash loop. | |||
There was a problem hiding this comment.
Looks good, just adjust the case please:
Suggested change
| When deployed with ECK, the Fleet Server pod makes an http call to itself during fleet initialization using its service endpoint. Since a link:https://github.com/kubernetes/minikube/issues/1568[pod cannot reach itself through its service on minikube] when CNI is disabled, the call hangs until the connection times out and the pod goes into a crash loop. | |
| When deployed with ECK, the Fleet Server Pod makes an HTTP call to itself during Fleet initialization using its Service. Since a link:https://github.com/kubernetes/minikube/issues/1568[Pod cannot reach itself through its Service on minikube] when CNI is disabled, the call hangs until the connection times out and the Pod enters a crash loop. |
There was a problem hiding this comment.
Thanks for the suggestion @thbkrkr.
Update docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
|
Jenkins test this please |
|
@elasticmachine run elasticsearch-ci/docs |
thbkrkr
approved these changes
Oct 14, 2022
thbkrkr
changed the title
naemono
pushed a commit
to naemono/cloud-on-k8s
that referenced
this pull request
Jan 9, 2023
Document that Fleet Server initialization fails on minikube when CNI is disabled. Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
naemono
added a commit
that referenced
this pull request
Jan 9, 2023
Document that Fleet Server initialization fails on minikube when CNI is disabled. Co-authored-by: Farhim Ferdous <37705070+AluBhorta@users.noreply.github.com> Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fleet Server initialization fails on minikube when CNI is disabled.