Skip to content

[EPIC] Support air-gapped installation #173

Closed as not planned
Closed as not planned

Description

@nbykov0

Steps:

  • add a script which would collect images for each package
  • add a script which would build/push images to private repo with correct names
  • add nessesary stuff to packages' helm charts so that default images and pullSecrets could be overridden from a single point

Activity

  1. linked a pull request that will close this issueAirgapped install support #175on Jun 19, 2024
  2. NickVolynkin commented on Mar 25, 2025

    @NickVolynkin
    Contributor

    Related issue: #286

  3. NickVolynkin commented on Mar 25, 2025

    @NickVolynkin
    Contributor

    Options:

    • Full air-gap-ready distributive, with all images included
    • Script that downloads all required for installation, then user can move it to an air-gapped infra and deploy there
  4. changed the title [-]Support air-gapped installation[/-] [+][EPIC] Support air-gapped installation[/+] on Apr 3, 2025
  5. NickVolynkin commented on Apr 3, 2025

    @NickVolynkin
    Contributor

    This feature is valuable for large teams. There's a lot of work to do, so it should be an epic, split into multiple smaller issues.

  6. dosubot commented on Oct 19, 2025

    @dosubot

    Hi, Nikita (@nbykov0). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You proposed adding support for air-gapped installations by creating scripts to collect and push package images to private repositories.
    • You also suggested updating Helm charts to allow image and pull secret overrides.
    • A maintainer acknowledged the value of this feature, especially for large teams, and referenced a related issue.
    • The maintainer recommended breaking this feature into an epic with smaller, manageable issues for implementation.
    • The issue remains unresolved with no recent updates.

    Next Steps:

    • Please let me know if this issue is still relevant to the latest version of the cozystack repository by commenting here.
    • If I don’t hear back within 7 days, I will automatically close this issue.

    Thank you for your understanding and contribution!

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 19, 2025
  8. nbykov0 commented on Oct 20, 2025

    @nbykov0
    CollaboratorAuthor

    Work is currently on hold but this feature is not abandoned.

  9. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Oct 20, 2025
  10. kvaps commented on Oct 20, 2025

    @kvaps
    Member

    We have support for air-gapped environments

    main doc: https://cozystack.io/docs/install/kubernetes/air-gapped/

  11. nbykov0 commented on Oct 22, 2025

    @nbykov0
    CollaboratorAuthor

    Andrei Kvapil (@kvaps) this epic is about implementing a dedicated docker registry for every image, and related stuff.

  12. dosubot commented on Jan 21, 2026

    @dosubot

    Hi, Nikita (@nbykov0). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.

    Issue Summary:

    • You proposed adding air-gapped installation support by creating scripts for collecting and pushing container images to private registries and updating Helm charts for image and pull secret overrides.
    • Maintainer NickVolynkin recognized the feature's value and suggested breaking it into an epic with smaller issues.
    • You confirmed the work is currently on hold but not abandoned.
    • Another maintainer noted existing air-gapped environment support, but you clarified this issue targets dedicated registries per image and related tasks.
    • The issue remains unresolved with no recent activity.

    Next Steps:

    • Please let me know if this issue is still relevant to the latest version of the cozystack repository by commenting here to keep the discussion open.
    • Otherwise, I will automatically close this issue in 7 days.

    Thank you for your understanding and contribution!

  13. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Jan 21, 2026
  14. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale
    on Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions