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

Added helm charts. #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Added helm charts. #13

wants to merge 1 commit into from

Conversation

fplk
Copy link
Contributor

@fplk fplk commented Jan 14, 2019

However, these helm charts only seem to work for IBM Cloud as does the standard installation procedure of the driver. With DIND Kubernetes I run into issues - will open a separate bug issue with a workaround.

@@ -0,0 +1,10 @@
replicaCount: 1
image:
repository: ffdl/ibmcloud-object-storage-plugin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the registry belongs to ffdl project. Is ffdl updating the image regularly?
I think better need to document the steps to create image and push to registry and then how to use the chart to deploy plug-in

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FfDL image is only updated sporadically - one reason for migrating the helm charts. It probably makes sense to maintain images as part of this project [which is, of course, not up to me to decide].

apiVersion: v1
description: A Helm chart for ibmcloud-object-storage plugin
name: ibmcloud-object-storage-plugin
version: 0.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think same charts are available under https://github.com/IBM/FfDL/blob/master/storage-plugin/Chart.yaml
I think better to keep chart at one place.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completely agree. Since there are almost certainly more people who want to deploy the driver with Helm than just FfDL, it should make sense to maintain the helm charts in the driver repository rather than FfDL.

hostPath:
path: /run/systemd
imagePullSecrets:
- name: regcred
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is regcred for FFDL registry?
I think the steps to create image, push image and create image pull secrets from privet registry should be documented.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation sounds good. regcred is a Kubernetes pull secret for the registry that you create via

kubectl create secret docker-registry regcred --docker-server=${DOCKER_REPO} --docker-username=${DOCKER_REPO_USER} --docker-password=${DOCKER_REPO_PASS} --docker-email=unknown@docker.io

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants