terraform-k8s-stack-pachyderm-minio
Combinator.ml stack comprising of Pachyderm backed by Minio .
This could be used as a module, but it is intended as a self-contained stack.
KUBE_CONFIG_PATH=~ /.kube/config terraform apply
KUBE_CONFIG_PATH=~ /.kube/config terraform destroy
Why do you have to explicitly export the Kubernetes config?
I found that hardcoding the kubeconfig led to this terraform bug .
Left over CertificateSigningRequests
If you see errors about pods not being able to mouht TLS secrets, it's probably because it's trying to reuse an old set of secrets set up in a previous CertificateSigningRequest. Delete all the old CertificateSigningRequests and try again.
kubectl delete certificatesigningrequests.certificates.k8s.io minio-tenant-default-csr minio-tenant-console-default-csr
Name
Version
kubectl
~> 1.10.0
provider
~> 2.1.0
Name
Version
kubernetes
n/a
Name
Source
Version
minio
combinator-ml/minio/k8s
0.0.2
pachyderm
combinator-ml/pachyderm/k8s
0.0.1
Name
Description
Type
Default
Required
namespace
(Optional) The namespace to install the release into. Defaults to default
string
"default"
no
pachyderm_bucket_name
(Optional) the name of the bucket in minio to store Pachyderm data (must be bucket name compliant)
string
"pachyderm-data"
no
Name
Description
CONSOLE_ACCESS_KEY
Minio console username.
CONSOLE_SECRET_KEY
Minio console password
MINIO_ROOT_PASSWORD
Minio root password
MINIO_ROOT_USER
Minio root username.
tenant_namespace
Namespace is the kubernetes namespace of the minio operator.