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

Cannot apply policy to Minikube context #283

Open
Jeffertron opened this issue Apr 10, 2018 · 1 comment
Open

Cannot apply policy to Minikube context #283

Jeffertron opened this issue Apr 10, 2018 · 1 comment
Assignees
Labels

Comments

@Jeffertron
Copy link
Contributor

I followed the instructions (https://github.com/Aptomi/aptomi/blob/master/docs/k8s_minikube.md) for running k8s on my local machine using Minikube v0.25.2.

Unfortunately, when I input this command in step 2:
aptomictl gen cluster -n cluster-us-east -c minikube -N east | aptomictl policy apply -f -

...I receive the following error from the Aptomi server:

ERRO[4341] Error while serving request: Error while validating cluster cluster-us-east of type kubernetes: error during init: could not get kubernetes config for cluster cluster-us-east: invalid configuration: [unable to read client-cert /home/jeffertron/.minikube/client.crt for minikube due to open /home/jeffertron/.minikube/client.crt: no such file or directory, unable to read client-key /home/jeffertron/.minikube/client.key for minikube due to open /home/jeffertron/.minikube/client.key: no such file or directory, unable to read certificate-authority /home/jeffertron/.minikube/ca.crt for minikube due to open /home/jeffertron/.minikube/ca.crt: no such file or directory]

After inputting each of the two commands separately, the command before the pipe works, but the command after the pipe gives me that error every time.

@romangithub1024 romangithub1024 added this to the Week ending Apr 8, 2018 milestone Apr 10, 2018
@romangithub1024
Copy link
Contributor

@Frostman can you take a look? sounds like we are uploading YAML with local paths to keys/certs, and it can't be validated

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

No branches or pull requests

3 participants