Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instructions fail when LoadBalancer service defines a hostname instead of an IP for the LB ingress #133

Open
3 tasks
izgeri opened this issue Jan 19, 2021 · 0 comments

Comments

@izgeri
Copy link
Contributor

izgeri commented Jan 19, 2021

Summary

When you install the helm chart, the instructions tell you to get the service IP by running:

export SERVICE_IP=$(kubectl get svc --namespace geri-conjur-test \
>                                           geri-conjur-oss-ingress \
>                                           -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

My service didn't have an IP, however - I actually needed to run

export SERVICE_IP=$(kubectl get svc --namespace geri-conjur-test \
>                                           geri-conjur-oss-ingress \
>                                           -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')

to get the EXTERNAL-IP for my Conjur instance.

Steps to Reproduce

Run the following command in OpenShift 4.3, where you've set CONJUR_NAMESPACE, DATA_KEY, and HELM_RELEASE locally following the docs.

helm install \
   -n "$CONJUR_NAMESPACE" \
   --set image.repository=registry.connect.redhat.com/cyberark/conjur \
   --set image.tag=latest \
   --set nginx.image.repository=registry.connect.redhat.com/cyberark/conjur-nginx \
   --set nginx.image.tag=latest \
   --set postgres.image.repository=registry.redhat.io/rhscl/postgresql-10-rhel7 \
   --set postgres.image.tag=latest \
   --set openshift.enabled=true \
   --set dataKey="$DATA_KEY" \
   "$HELM_RELEASE"  \
   https://github.com/cyberark/conjur-oss-helm-chart/releases/download/v2.0.3/conjur-oss-2.0.3.tgz

Expected Results

Running the command to extract the service IP works once the loadbalancer IP is available.

Actual Results (including error logs, if applicable)

The value is empty, because it expects IP instead of hostname in the jsonpath.

Reproducible

  • Always
  • Sometimes
  • Non-Reproducible

Version/Tag number

See command above.

Environment setup

OCP 4.3.

Additional Information

  • I didn't try it this way, but what if you are using a NodePort service instead of the LoadBalancer? Are the instructions still valid?
  • It's also worth noting that HELM_RELEASE is not defined in the docs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant