mayadata-io / mayadata-io/kubera-api-testing

refactor: use kubernetes custom resource to execute helm install

Open
#11 0 comments 0 reactions 1 assignee View on GitHub

@amitbhatt818 is already working on this.

Since Sep 2, 2020.

Dominant language
Go
Stars
3
Forks
4
PR merge metrics
No merged PRs in 30d

Description

**_ProblemStatement_**: I want to simplify below codebase by dividing them into two separate blocks where each block is embedded into specific Kubernetes custom resources. These custom resources should be invoked only if they satisfy the eligibility criteria. These custom resources are engineered to handle executing the terminal commands as well as their outputs _(stdop, stderr, streaming, timeout, retries, etc)_.

```sh
if [ "$USE_KUBERA_REPO" == "true" ]
then

echo -e "\nDeploying Kubera using kubera-charts repo\n"
echo -e "\nCloning $KUBERA_BRANCH branch of kubera-charts repo\n"
git clone -b "$KUBERA_BRANCH" https://"$GIT_USERNAME":"$GIT_PASSWORD"@github.com/mayadata-io/kubera-charts.git
cd kubera-charts

echo -e "\nSet release version,openebsRCEnable,maxMemberCountInOneProject and URL"
echo -e "\nInstalling Kubera using kubera-charts/values.yaml"
helm install --namespace kubera kubera \
--set server.url="$URL" \
--set server.release="$RELEASE" \
--set server.openebsRCEnable=true \
--set server.maxMemberCountInOneProject=50 -f values.yaml .

else

echo -e "\nDeploying Kubera using official Kubera charts\n"
helm repo update

echo -e "\nAdd kubera in local repository"
helm repo add kubera https://charts.mayadata.io/

echo -e "\nApply helm chart"
helm install kubera kubera/kubera-charts \
--set server.url="$URL" \
--set server.release="$RELEASE" \
--set server.maxMemberCountInOneProject=100 \
--set server.openebsRCEnable=true \
-n kubera

fi
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.