Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fastly: use a private bucket as origin for dl.k8s.io #7178

Merged
merged 2 commits into from
Aug 19, 2024
Merged

Fastly: use a private bucket as origin for dl.k8s.io #7178

merged 2 commits into from
Aug 19, 2024

Commits on Aug 14, 2024

  1. fastly: use a private bucket as origin for dl.k8s.io 

    - Ensure the VCL service can use a GCS private bucket as origin using AWS
auth headers. GCS API is S3-compatible. We apply the snippet from https://quic.fastly.com/documentation/solutions/examples/google-cloud-storage-origin-private/
- Enable Shielding for the service. More informations on https://www.fastly.com/documentation/guides/concepts/shielding/
- Disable the healthcheck for the service. This is not required since we
  have Origin Inspector activated and is currently not working with the
  private bucket.

Signed-off-by: Arnaud Meukam <[email protected]>
    @ameukam
    ameukam committed Aug 14, 2024
    Configuration menu
    Copy the full SHA
    00af19b View commit details
    Browse the repository at this point in the history

  2. Use hmac key credentials for gcs auth 

    Add data resources that will help get the credentials needed for the VCL
to authenticate against GCS API.

Signed-off-by: Arnaud Meukam <[email protected]>
    @ameukam
    ameukam committed Aug 14, 2024
    Configuration menu
    Copy the full SHA
    028f89e View commit details
    Browse the repository at this point in the history