Updated upstream repo & app style for jenkins, minio and grafana

[nitishkumar71]

Signed-off-by: Nitishkumar Singh [email protected]

New Upstream repo urls has been updated for jenkins, minio and grafana

Description

Motivation and Context

• I have raised an issue to propose this change (required)
  relates Notice: the stable Helm charts have been deprecated, new alternatives are required #274

How Has This Been Tested?

Jenkins

1. Install Jenkins
   arkade install jenkins

2. Get Credentials

export USER=$(kubectl get secret jenkins \
        -o jsonpath="{.data.jenkins-admin-user}" | base64 --decode)
export PASS=$(kubectl get secret jenkins \
        -o jsonpath="{.data.jenkins-admin-password}" | base64 --decode)
echo "Credentials: $USER / $PASS"

3. Port-forward the Jenkins service
   kubectl port-forward svc/jenkins 8080:8080 &

4. Open the Jenkins UI at:
   echo http://127.0.0.1:8080

5. Use Credentials obtained in step 2 for login

minio

1. Install minio
   arkade install minio

2. Forward the minio port to your machine
   kubectl port-forward -n default svc/minio 9000:9000 &

3. Get the access and secret key to gain access to minio

ACCESSKEY=$(kubectl get secret -n default minio -o jsonpath="{.data.accesskey}" | base64 --decode; echo)
SECRETKEY=$(kubectl get secret -n default minio -o jsonpath="{.data.secretkey}" | base64 --decode; echo)

4. Get the Minio Client

curl -SLf https://dl.min.io/client/mc/release/linux-amd64/mc \
  && chmod +x mc

5. Add a host
   mc config host add minio http://127.0.0.1:9000 $ACCESSKEY $SECRETKEY
6. List buckets
   mc ls minio

Grafana

1. Install grafana
   arkade install grafana

2. Get the admin password:
   kubectl get secret --namespace grafana grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo

3. Expose the service via port-forward:
   kubectl --namespace grafana port-forward service/grafana 3000:80

4. Use credential obtained in step2 with username admin to login on grafana

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s
• I have added tests to cover my changes.
• All new and existing tests passed.

• I have tested this on arm, or have added code to prevent deployment

[nitishkumar71]

@alexellis @Waterdrips Can you please review it?

[Waterdrips]

can we add the --set flag to this app, then merge the set values with overrides just before calling the install?

[nitishkumar71]

@Waterdrips Since we are using helm version v3.1.2 in arkade. Grafana helm charts above 6.0.0 recommend helm version >= 3.4.0. I think which is why the grafana version was hardcoded earlier itself.

Possibly @aidun can put some more lights on it.

[alexellis]

There are some charts that won't install with a newer helm version. The Grafana chart may recommend 3.4.0, but is it a hard requirement?

[nitishkumar71]

I tried it and nothing broke in installation. Not sure, why the recommendation from grafana team. helm 3.4.0 is recommended for chart from 6.0.0

[alexellis]

Could you move the error handling into PreRunE - there are some examples you can follow in the code elsewhere.

[nitishkumar71]

Done

[alexellis]

@Waterdrips please can you give this a final pass?

[Waterdrips]

LGTM