search

pivotal / docs-tas-adapter

2 stars 5 forks source link

Instructions to install tas-adapter to air-gapped environments #26

Closed akrishna90 closed 2 years ago

akrishna90 commented 2 years ago

Is there a related Issue?

TME-1698

What is this change about?

Adds a new markdown file with instruction to install tas-adapter to air-gapped envs

Acceptance Steps

see jira issue TME-1698

cf-gitbot commented 2 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

davewalter commented 2 years ago

It might be a good idea to duplicate the strategy from the TAP docs where they always recommend that the user relocates the images to their own registry, regardless of whether they are attempting to install in an air-gapped environment or not.

This would also help to remove the duplication of having two separate installation docs.

tcdowney commented 2 years ago

@davewalter I think that makes sense, but could be a separate story IMO. I think this one is a good starting place and then we could unify the two.

emalm commented 2 years ago

Yeah, sounds fine to merge this and we can adjust the organizational structure before the next release. In general, we've found that it's best to keep the installation flow as linear as possible, as every jump or tangent is an opportunity to derail the process.

I could see package relocation being an optional/recommended step before installation in the main sequence, and then parametrizing the install-registry location/creds to allow the operator to install either directly from TanzuNet or from the relocation destination.