docs(eck): add guide for deploying Elasticsearch and Kibana with ECK on ACP 4.4 - #851
Merged
Merged
Conversation
…on ACP 4.4 Verified on ACP 4.4 / Kubernetes 1.35 (amd64) with ECK 3.4.1 and Elasticsearch/Kibana 9.5.4: mirror Elastic's images to the platform registry, rewrite the operator image and the operator's container-registry default, create a single-node Elasticsearch and a Kibana, verify over in-cluster HTTPS, and uninstall. Registries that require a pull secret are documented from upstream and marked as not verified. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds a new How-To guide (en + zh) for deploying Elasticsearch and Kibana on ACP with Elastic Cloud on Kubernetes (ECK), Elastic's own operator.
Verified on ACP 4.4 / Kubernetes 1.35 (amd64) with ECK 3.4.1 and Elasticsearch / Kibana 9.5.4:
container-registrydefault, so theElasticsearch/Kibanaresources need nospec.imagegreen; in-cluster HTTPS query and an index-and-search round tripDocumented from upstream, marked as not verified in the guide: registries that need a pull secret, multi-node topologies, external access, arm64, other StorageClasses, upgrades.
The guide does not repackage anything; it points to Elastic's published manifests and images and links Elastic's licensing page.
id/sourceSHAfront-matter is left for the repo's workflow to stamp.🤖 Generated with Claude Code