A Kubernetes Operator to prepare the OpenShift workshop infrastructure for running Red Hat Developers Workshops
|
Important
|
The Operator is under development and may undergo rapid changes |
oc new-project rhd-workshop-infra
oc apply -n rhd-workshop-infra -f deploy/service_account.yaml
oc apply -n rhd-workshop-infra -f deploy/role.yaml
oc apply -n rhd-workshop-infra -f deploy/role_binding.yaml
oc apply -n rhd-workshop-infra -f deploy/crds/developers_v1alpha1_workshop_crd.yaml
oc apply -n rhd-workshop-infra -f deploy/operator.yamlThe following attributes are configurable via CR
-
delete_workshop: flag to delete the workshop, defaultFalse -
openshift_api_server: the openshift authentication serveroauth-openshift.openshift-authentication:6443 -
create_projects: flag to control whether to create workshop user OpenShift projects or not -
projects: its the list of OpenShift that need to be created for each user
The user specific configurations
-
create: Flag to create users or not, default:false -
prefix: The prefix for the user, defaults touser -
password: The password for workshop users, defaultsopenshift -
admin_password: The OpenShift cluster-admin password defaultssuperS3ret -
from: The start range of users count, defaults to0 -
to: The end range of users count, defaults to50
The software packages to install, by default Eclipse Che will be installed.
|
Note
|
All software packages will be installed using Kubernetes Operators. Please check Operator Hub for more information |
che_version: The Eclipse Che version to be used.
install: Whether to install the software stacks or not, defaults to true
The stacks divided based on community and redhat operators
The operator uses community-operators as the source for the following packages:
-
knative-serving -
knative-eventing -
openshift-pipelines
Create an custom resource called Workshop, checkout the Example