Create an offline snapshot for air-gapped installation docs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 105
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
Why?
We have a group of customers that need to view all air-gapped installation docs in a single location. Since these customers don't have access to public internet, we should provide them with an offline snapshot of these air-gapped install docs.
Existing air-gapped installation docs and current owners
- Logstash (David K and Karen): https://www.elastic.co/guide/en/logstash/8.5/plugins-filters-geoip.html#plugins-filters-geoip-manage_update
- Logstash maybe (David K and Karen): https://www.elastic.co/guide/en/logstash/current/offline-plugins.html
- Fleet and Elastic Agent Guide (Karen): https://www.elastic.co/guide/en/fleet/current/air-gapped.html
- Fleet and Elastic Agent (Karen): https://www.elastic.co/guide/en/fleet/7.17/fleet-overview.html#package-registry-intro
- Elastic Cloud on Kubernetes (Arianna): https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-air-gapped.html
- ECE (Arianna): https://www.elastic.co/guide/en/cloud-enterprise/3.5/ece-install-offline.html
Supporting docs
- https://discuss.elastic.co/t/upgrading-elastic-agent-via-fleet-in-an-air-gapped-environment-failing/297413
- https://github.com/wise2c-devops/install-elastic-cloud-on-k8s
- https://github.com/elastic/kibana/issues/74614
Discussion points
- External dependencies
- Offline doc ownership
- Breaking changes ownership
- Potential home: Elastic Installation and Upgrade Guide
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the listed Logstash, Fleet and Elastic Agent, ECK, and ECE air-gapped installation pages, along with the supporting links. Start by mapping external dependencies, ownership, and breaking-change responsibility, then evaluate the proposed Elastic Installation and Upgrade Guide location. Done means customers can access all relevant air-gapped installation documentation in one offline snapshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100