You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RH-SSO Openshift Container Patch - appliable for Developer templates only!
Compatibility -> 7.6.0.GA or latest
Clone this patch repository and push it to your git web repository manager e.g. Github, Gitlab etc.
Replace patch.zip with the desired patch (defaults to 7.6.6 no-op patch from generate-noop-patch.sh).
Update sso-patch_buildconfig.yaml:
Change dockerStrategy from version if required (defaults to RH-SSO 7.6)
Change git uri to your cloned repository (defaults to the original)
Update Dockerfile (if you need to use different parent image)
FROM <<your_parent_image>>
Add, commit, and push your changes to your copy of this repo.
Run CLI login command. Copy command shown on this page https://{{openshifthostnamegoeshere}}/oauth/token/request.
{{openshifthostnamegoeshere}} => replace it with your Openshift instance hostname
oc project projnamegoeshere to select your project
oc policy add-role-to-user system:image-puller system:serviceaccount:$(oc project -q):default --namespace=openshift to allow official image to be pulled into your project
oc create -f sso-patch_imagestream.yaml to setup output stream for your image
oc create -f sso-patch_buildconfig.yaml to install patch buildconfig
Image should automatically start building, but if not use oc start-build sso-patch.
Wait for image to build, if successful it will be added as sso-patch:latest.
Edit your application's deployment config and replace the name (triggers section) value with: sso-patch:latest, and also change the lastTriggeredImage (triggers section) and image (containers section) variables to image-registry.openshift-image-registry.svc:5000/{{projnamegoeshere}}/sso-patch:latest value.
{{projnamegoeshere}} => replace it with your project name
Save the deployment config change and reload it. Check the project pods, you will notice that SSO container was restarted.
Open the SSO pod terminal and run this commands to check wheater the patch was applied successfully: