redhat-developer / redhat-developer/mapt
[Feature] Ensure we can use airgap scenario in snc offering
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
We offer --airgap flag as part of VMs in AWS, it uses same logic based in 2 phases, allowing a intial phase with external connectivity to setup the machine and a second where routes are removed so machine external connectivy is cut off
Ensure we can use this flag and same approach for openshfit-snc
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
Start by locating the existing --airgap handling for AWS VMs and the openshift-snc offering entry point. Trace how the two phases are represented, then verify that openshift-snc permits initial external connectivity before removing routes; done means the same airgap workflow is available for that offering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100