-
Notifications
You must be signed in to change notification settings - Fork 4
Instructions for admin
Development:
- Manage owner/admins: https://webservices-portal.web.cern.ch/paas/alcaval-dev
- Openshift resources: https://paas.cern.ch/k8s/cluster/projects/alcaval-dev
- People with manager role: alcaval-dev-managers
- Admin group: alcaval-admin-group
- OIDC registration: https://application-portal.web.cern.ch/manage/08da3c9b-1e0d-4eb5-8d4d-e34323419553
Production:
- Manage owner/admins: https://webservices-portal.web.cern.ch/paas/alcaval
- Openshift resources: https://paas.cern.ch/k8s/cluster/projects/alcaval
- People with manager role: alcaval-managers
- Admin group: alcaval-admin-group
- OIDC registration: https://application-portal.web.cern.ch/manage/08da14d5-9b16-4cf1-8772-c51d2e771fd4
Sensitive data provided to the application via secrets and it can be modified from here:
Prod: https://paas.cern.ch/k8s/ns/alcaval-dev/secrets/client-secret-file
Dev: https://paas.cern.ch/k8s/ns/alcaval-dev/secrets/client-secret-file
Once you modify any secret, you will need to re-deploy the application from:
Prod: DeploymentConfig
Dev: DeploymentConfig
Click on Actions -> Start rollout.
When any changes are pushed to dev or main branch of the repository, application will be restarted automatically. This is because it is triggered by web-hooks. In case web-hooks are not functioning, you can restart the application using following links.
Prod: https://paas.cern.ch/k8s/ns/alcaval/buildconfigs/alcaval
Dev: https://paas.cern.ch/k8s/ns/alcaval-dev/buildconfigs/alcaval-dev
Click on Actions -> Start build to restart the build manually.
Whenever you find application not performing as expected. You can quickly reset currently running pod from here:
https://paas.cern.ch/k8s/ns/alcaval/deploymentconfigs/alcaval
Scale down pod count to 0 then again scale up count to 1. This will create fresh instance which might help you resolving unexpected behavior. Note that this does not fetch any data from GitHub repo.