Skip to content

Commit

Permalink
chore: document image creation process
Browse files Browse the repository at this point in the history
  • Loading branch information
thegentlemanphysicist committed Jan 24, 2025
1 parent c35c66d commit 457ee2c
Showing 1 changed file with 25 additions and 0 deletions.
25 changes: 25 additions & 0 deletions docker/keycloak/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,31 @@ The `configuration` directory contains the pre-defined Keycloak configuration to
1. Replace token cache mechanism `distributed-cache` with `replicated-cache` to ensure the token availability through multiple pods.
1. Enable `manual` upgrading of the database schema instead of auto-upgrading.

## Building docker images locally

For testing purposes it is often neccesary to build a local version of the keycloak image and push it directly to the registry. This will require access to the redhat registry:

```
docker login registry.redhat.io
```

Credentials are stored in openshift secrets.

To build the image locally, go to the `sso-keycloak/docker/keycloak/` folder and run:

```
docker build . -f <<dokerfile_name>> -t ghcr.io/bcgov/sso:<<test-tag>>
```

Publishing the taged image to the sso-switchover-agent repos requires two steps:

Login to the ghcr, a guide can be found here: [github guide](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry)

Pushing the image to the repo:

```
docker push ghcr.io/bcgov/sso:<<testtag>>
```
## Custom extensions

### Authentications
Expand Down

0 comments on commit 457ee2c

Please sign in to comment.