Skip to content

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

@izgeri

Description

@izgeri

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions