feat(vnets) add peering and subnet to allow ci.jenkins.io to spawn VM agents in the new subscription #172
Conversation
This file contains 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
… agents in the new subscription Signed-off-by: Damien Duportal <[email protected]>
lemeurherve
approved these changes
Nov 17, 2023
lemeurherve
reviewed
Nov 17, 2023
|
|
dduportal
deleted the
feat/helpdesk-3818/add-sponsorship-subscription-cijenkinsio-agents
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to jenkins-infra/helpdesk#3818
This PR adds 2 new resources to allow ci.jenkins.io to spin up VM agents in the new "public-jenkins-sponsorship" VNET:
Peering between the
publicvnet and this new vnet to ensure controller and agents can communicate with each other without requiring a public IP (agent -> controller is OK for ci.jenkins.io because it is a public service but using private IP for agents is a requirement so the controller should be able to contact these private VMs).Add a subnet in the new vnet for ci.jenkins.io agents. Same sizing as the current one: max 512 IPs in the subnet (a BOM build is 300 agents, an ATH build is ~20 agents)