SiteMinder Policy Server container ends up in CrashçLoopBackOff after deployment

Products

• SITEMINDER

Issue/Introduction

Running

helm upgrade --install policyserver . -f values.yaml -n ssoe-inte-bck --set policyServer.enabled=true --set admin.enabled=true --version "12.9.000+3085"

with config-retriever enabled, pods get created but can't start and kubectl get pods shows the following:

policyserver-siteminder-admin-0                          0/2     Init:CrashLoopBackOff   5 (60s ago)   12m

policyserver-siteminder-policy-server-64d845bd75-x7p7t   0/2     Init:1/2                0             12m

Environment

CA SiteMinder for Containers, all versions

Cause

Misconfiguration of the bitbucket connection method in source section for config retriever sidecar may cause this problem.

For instance:

configuration:
  source:
  "ssh://[email protected]:<port>/<namespace>/siteminderintegracion.git;master"
 gitFolderPath: "/SiteminderConfiguration"
runtimeConfiguration:
  enabled: true
  source: "ssh://[email protected]:<port>/<namespace>/siteminderintegracion.git;master"
  runtimeGitFolderPath: "/SiteminderRunTimeConfiguration"

will end up in this state as ssh is not a supported bitbucket connection method

Resolution

Make sure that you specify https as the connection method for bitbucket