-
Notifications
You must be signed in to change notification settings - Fork 826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud provider ASNs store #1914
Comments
I wonder if we could prioritise vendors from this list? |
@BobyMCbobs Feel free to open a PR about this. I would suggest you to centralize those ASNs in a dedicated folder (maybe |
Vendor ASN PRs:
|
@BobyMCbobs I'll move those files to a dedicated folder as a followup. It'll help simplify the approval for any change related to this issue. |
Thank you, @ameukam! |
/close |
@ameukam: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'd like to create a folder in this repo to manage the known ASNs for each CNCF-supported cloud-provider. This will mean for query-able IP blocks that will end up being used with a 302-redirect or split-horizon DNS for {artifacts,registry}.k8s.io.
Examples:
(so forth...)
It would be lovely to also have a representative from each cloud-provider to ☑️ verify these ASNs represent their networks.
The text was updated successfully, but these errors were encountered: