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
Deploy conjur follower instance to openshift with kubernetes-conjur-deploy
Obtain follower pod logs, and see the error shown above.
Expected Results
No nill errors
Actual Results (including error logs, if applicable)
See the logs shown above
Reproducible
Always
Sometimes
Non-Reproducible
I have reproduced this multiple times, but the kubernetes-conjur-deploy build still works, so maybe this is a usecase that isn't tested by the pipeline for that repo.
Version/Tag number
Appliance 5.11.0
Environment setup
Conjur in ec2 via xa-cluster, k8s follower in oc 3.11 (Dev account) via kubernetes-conjur-deploy
@jonahx can you lend your Ruby expertise to help me understand why quotes around host.id in this file would make a difference to the error @hughsaunders is seeing above?
Uh oh!
There was an error while loading. Please reload this page.
Summary
When kubernetes-conjur-deploy deploys a follower pod in k8s, sometimes it fails to become ready and shows the following in the logs:
Steps to Reproduce
Steps to reproduce the behavior:
Expected Results
No nill errors
Actual Results (including error logs, if applicable)
See the logs shown above
Reproducible
I have reproduced this multiple times, but the kubernetes-conjur-deploy build still works, so maybe this is a usecase that isn't tested by the pipeline for that repo.
Version/Tag number
Appliance 5.11.0
Environment setup
Conjur in ec2 via xa-cluster, k8s follower in oc 3.11 (Dev account) via kubernetes-conjur-deploy
Additional Information
I have worked around this issue by manually changing
host.id
to"host.id"
on L164 and L177 of app/domain/authentication/authn_k8s/inject_client_cert.rb after deployment. This isn't ideal, but got the environment up and running.Related
The text was updated successfully, but these errors were encountered: