Bug 1406344
| Summary: | [cns-deploy] When using service account, No need to specify the Namespace in oc process for heketi deployment | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Mohamed Ashiq <mliyazud> |
| Component: | cns-deploy-tool | Assignee: | Raghavendra Talur <rtalur> |
| Status: | CLOSED ERRATA | QA Contact: | Prasanth <pprakash> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | cns-3.4 | CC: | bmohanra, hchiramm, jarrpa, mliyazud, rcyriac, vinug |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | CNS 3.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the user had to keep track of the namespace, and had to mention the namespace for heketi to contact the kube client using the namespace value. With this release, the user can get the Kuberenetes option to connect to kube client from the secret mounted in the heketi pod, resulting in better usability.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-20 18:26:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1415598 | ||
|
Description
Mohamed Ashiq
2016-12-20 10:30:08 UTC
The HEKETI_KUBE_NAMESPACE is not required as we can fetch the namespace from secret. This can be removed from the cns-deploy
# oc process deploy-heketi -v \
HEKETI_KUBE_NAMESPACE=${NAMESPACE} \
HEKETI_KUBE_INSECURE=y \
HEKETI_KUBE_SECRETNAME="${heketi_secret}" \
HEKETI_KUBE_APIHOST="${kubeapi}" | oc create -f -
(In reply to Humble Chirammal from comment #3) > https://github.com/gluster/gluster-kubernetes/issues/56 Discard above command, wrong paste. Patch upstream at https://github.com/gluster/gluster-kubernetes/pull/120 Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. This bz got closed due to a mistake in clearing dev-ack flag. Reopened and considering for CNS 3.5. Patch available and merged upstream at https://github.com/gluster/gluster-kubernetes/pull/112 (In reply to Raghavendra Talur from comment #12) > Patch available and merged upstream at > https://github.com/gluster/gluster-kubernetes/pull/112 Available with CNS 3.5 builds. Verified Edited the doc text for the errata and got it reviewed by Ashiq. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1112 Marking qe-test-coverage as - since the preferred mode of deployment is using ansible |