Normal Scheduled 7m21s default-scheduler Successfully assigned first-instance/datastore-db-798b77bd89-kxg9x to minikube
Warning Failed 4m57s (x12 over 7m16s) kubelet, minikube Error: secrets "ckan-env-vars" not found
So the reason is that secret ckan-env-vars does not exist. And there is not a single word about ckan-cloud-env in docs. Only place I found it is ckan-cloud-docker.
Q: How can I relate this 2 repos?
Create ckan-env-vars
So as it seems I have to work with ckan-cloud-docer as well. As it seems I need to have cca-operator running and is able to communicate with minkube. To do so I have to do the following according to README
Not sure why it assumes that directory should exist.
At this point, I'm quitting with non-centralized infra. After all, the cluster is controlled by ckan-cloud-helm and CCO, and there it's with centralized infra
As a developer, who follows the README, I expect to be able to deploy ckan image without centralized infra, But I'm not
Acceptance Criteriea
Tasks
Analysis
I've tried to deploy the ckan instance without centralized infra
But some pods won't start
Kubectl describe pods:
So the reason is that secret
ckan-env-vars
does not exist. And there is not a single word aboutckan-cloud-env
in docs. Only place I found it isckan-cloud-docker
.Q: How can I relate this 2 repos?
Create ckan-env-vars
So as it seems I have to work with ckan-cloud-docer as well. As it seems I need to have
cca-operator
running and is able to communicate with minkube. To do so I have to do the following according to README.docker-compose.override.yaml
does not seem to be working. I've tried to directly put volumes' values in docker-compose.yaml and it worked.I can say it worked as I can get the nodes
I was able create secrets as well. Run follwoing
At this point all containers are now working fine execpt SOLR.
seems like it's coming from here https://github.com/ViderumGlobal/ckan-cloud-helm/blob/master/ckan/templates/solr-deployment.yaml#L30-L31
Not sure why it assumes that directory should exist.
At this point, I'm quitting with non-centralized infra. After all, the cluster is controlled by ckan-cloud-helm and CCO, and there it's with centralized infra