2.3.1 SSL Cert failed to update for SCIM URL

Hi @KnowsNothing.

I can confirm that v2.4.1 of the SCIM bridge has been submitted to the DO app store. The new version should show as an available option once the DO team approves the release.

Given that this is for Digital Ocean it may be better to follow the steps using the interface provided through the dashboard. The following is an adapted version of our https://support.1password.com/scim-update/#digitalocean for Digital Ocean:

Access the Kubernetes Dashboard

1. Visit the https://cloud.digitalocean.com/kubernetes/clusters
2. Choose the cluster where the SCIM bridge is deployed
3. Click "Kubernetes Dashboard"

Scale down the resources

1. Select the op-scim-bridge namespace from the dropdown at the top of the screen
2. Select "Deployment" from the Workloads menu on the left
3. Select op-scim-bridge under the Deployments
4. Select "Scale resource" from the top menu (looks like ...)
5. Change "Desired replicas *" to 0
6. Click "Scale"
7. Select "Stateful Sets" from the Workloads menu on the left
8. Select op-scim-bridge-redis-master under the Stateful Sets
9. Select "Scale resource" from the top menu (looks like ...)
10. Change "Desired replicas *" to 0
11. Click "Scale"

Wait a few seconds for the resources to be scaled down.

Scale the resources back up (reverse of previous steps)

1. Ensure that you still have the op-scim-bridge namespace selected from the dropdown at the top of the screen
2. Select "Stateful Sets" from the Workloads menu on the left
3. Select op-scim-bridge-redis-master under the Stateful Sets
4. Select "Scale resource" from the top menu (looks like ...)
5. Change "Desired replicas *" to 1
6. Click "Scale"
7. Select "Deployment" from the Workloads menu on the left
8. Select op-scim-bridge under the Deployments
9. Select "Scale resource" from the top menu (looks like ...)
10. Change "Desired replicas *" to 1
11. Click "Scale"

It may take a minute or two for the bridge to come back online and obtain a new certificate.

I hear you regarding expanding our support articles, but for the most part the bridge should "just work" after being set up and continue to obtain new certificates automatically. Unfortunately this wasn't the case in this instance. We will definitely be investigating why the certificate wasn't automatically renewed and continue to monitor the new releases.