Skip to content

ECK: Add new Fleet recipe #2699

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ECK: Add new Fleet recipe #2699

wants to merge 1 commit into from

Conversation

pebrc
Copy link
Contributor

@pebrc pebrc commented Aug 25, 2025

Depends on elastic/cloud-on-k8s#8788

Add a new recipe for ECK managed Fleet servers after a recent support escalation that illustrated that users would benefit from additional guidance on how to set this up.

This example shows how to expose the Fleet Server to the outside world using a Kubernetes Ingress resource. The Fleet Server is configured to use custom TLS certificates, and all communications are secured with TLS. The same Fleet Server is also accessible from within the cluster, allowing agents to connect to it regardless of their location. Refer to the comments in the fleet-ingress-setup.yaml file for more details on how to set up the Ingress resource and TLS certificates to enable this configuration.

@pebrc pebrc requested a review from a team as a code owner August 25, 2025 15:04
@github-actions GitHub Actions
Copy link

🔍 Preview links for changed docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@shainaraskas shainaraskas shainaraskas approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@pebrc @shainaraskas