mirror of
https://github.com/pomerium/pomerium.git
synced 2025-08-04 01:09:36 +02:00
ci: rename master to main (#3045)
Co-authored-by: alexfornuto <afornuto@pomerium.com>
This commit is contained in:
parent
1238fa86b7
commit
0b0fba06b3
69 changed files with 165 additions and 165 deletions
|
@ -11,7 +11,7 @@ description: >-
|
|||
|
||||
# Securing Cloud Run endpoints
|
||||
|
||||
This recipe's sources can be found [on github](https://github.com/pomerium/pomerium/tree/master/examples/cloudrun)
|
||||
This recipe's sources can be found [on github](https://github.com/pomerium/pomerium/tree/main/examples/cloudrun)
|
||||
|
||||
## Background
|
||||
|
||||
|
@ -38,7 +38,7 @@ This guide assumes you have Editor access to a Google Cloud project which can be
|
|||
|
||||
To deploy Pomerium to Cloud Run securely and easily, a special [image](https://console.cloud.google.com/gcr/images/pomerium-io/GLOBAL/pomerium) is available at `gcr.io/pomerium-io/pomerium:[version]-cloudrun`. It allows sourcing configuration from GCP Secrets Manager, and sets some defaults for Cloud Run to keep configuration minimal. We will be leveraging it in this example to store IdP credentials. Our policy contains no secrets so we can place it directly in an ENV var.
|
||||
|
||||
[Dockerfile](https://github.com/pomerium/pomerium/blob/master/.github/Dockerfile-cloudrun) Based on [vals-entrypoint](https://github.com/pomerium/vals-entrypoint)
|
||||
[Dockerfile](https://github.com/pomerium/pomerium/blob/main/.github/Dockerfile-cloudrun) Based on [vals-entrypoint](https://github.com/pomerium/vals-entrypoint)
|
||||
|
||||
The image expects a config file at `/pomerium/config.yaml`. Set `VALS_FILES=[secretref]:/pomerium/config.yaml` and set any other Pomerium Environment Variables directly or with secret refs such as `ref+gcpsecrets://PROJECT/SECRET(#/key])`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue