Update list of IPs restricted to VPN access only #376
Merged
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
![jenkins-infra-updatecli[bot]](https://avatars.githubusercontent.com/in/178728?s=60&v=4){kind=small}
... VPN CLI Made with ❤️️ by updatecli
Made with ❤️️ by updatecli
dduportal
approved these changes
Dec 12, 2024
dduportal
deleted the
updatecli_main_eadb8cdae5cf18d2df3727a07695464737032664703749579d974df8ceb26eb7
branch
dduportal
added a commit
to jenkins-infra/azure
that referenced
this pull request
Dec 18, 2024
…rraform from admin machines through VPN (instead of SSH tunnels) (#905) Following work and discoveries by @smerle33 in jenkins-infra/docker-openvpn#375 and jenkins-infra/docker-openvpn#376 This PR corrects and documents the required accesses to allow us running `terraform plan` (before sending PRs) and `terraform apply` (hotfix/emergencies) from our admin machines. - DBs routing is now fixed and using the VPN: documenting that `/etc/hosts` need to be updated (instead of using SSH tunnels) or using private subnets (infra.ci agents) - Adding back the Update Center storage account IP restriction to the admin public IPs to avoid errors Signed-off-by: Damien Duportal <[email protected]>
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.
Update list of IPs restricted to VPN access only & update vnets
Update public-db vnet IP in the YAML configuration of our OpenVPN CLI
change detected: * key "$.networks[0].routes[2]" updated from "10.252.0.0/21" to "10.253.0.0/21", in file "config.yaml"
Update public-db vnet IP in the user CCD routing configurations
9 file(s) updated with "# public-db vnet\npush \"route 10.253.0.0 255.255.248.0\"\n": * cert/ccd/private/danielbeck * cert/ccd/private/dduportal * cert/ccd/private/kevingrdj * cert/ccd/private/notmyfault * cert/ccd/private/smerle * cert/ccd/private/wfollonier * cert/ccd/private/krisstern * cert/ccd/private/markewaite * cert/ccd/private/timja
Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!