Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/docs/20-admins/20-installation/20-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,11 @@ The file above is just an example you will have to modify the options shown as f

- Label the node(s) you want to use for the builds with `renku.io/node-purpose: image-build`

### Build strategy

The last action required to have your system ready is to deploy the [BuildStrategy
for Shipwright](https://github.com/SwissDataScienceCenter/renku-data-services/blob/main/components/renku_pack_builder/manifests/buildstrategy.yaml).

### Configuration without Harbor and Shipwright

This is the default and no further steps are needed.
45 changes: 26 additions & 19 deletions docs/docs/20-admins/40-openshift/10-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -208,25 +208,6 @@ As an admin, setup renku project admin roles:
oc apply -f renku-roles.yaml
```

## Renku deployment

With everything in place as listed in the previous steps, Renku can now be
installed as usual

```bash
helm upgrade --install --namespace renku renku renk/renku -f renku-values.yaml --timeout 1800s --skip-crds
```

:::info

Any Renku user can be made a Renku administrator. This is useful for setting up
different global environments, resource pools or integrations. In addition,
Renku administrators can access the projects and similar resources of any user
in the platform. The documentation for assigning the Renku administrator role
can be found [here](../operation/user-management).

:::

### Amalthea session service account

The default Security Context Constraint (SCC) used to start pods will not allow
Expand Down Expand Up @@ -328,3 +309,29 @@ networkPolicies:
- ipBlock:
cidr: 172.31.0.0/16
```

## Renku deployment

With everything in place as listed in the previous steps, Renku can now be
installed as usual

```bash
helm upgrade --install --namespace renku renku renk/renku -f renku-values.yaml --timeout 1800s --skip-crds
```

:::info

Any Renku user can be made a Renku administrator. This is useful for setting up
different global environments, resource pools or integrations. In addition,
Renku administrators can access the projects and similar resources of any user
in the platform. Read more at [Managing Renku Admin Users](/docs/admins/operation/user-management#managing-renku-admin-users).

:::

## Image building

Based on Shipwright, OpenShift has a project called [Build for RedHat OpenShift](https://docs.redhat.com/en/documentation/builds_for_red_hat_openshift)
that provides all the necessary pieces to enable building images for the Renku platform.

Once the operator is installed, follow the [Harbor and Shipwright](/docs/admins/installation/configuration#harbor-and-shipwright)
instructions to get your system ready to build user session images.
Loading