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.

Sign up for GitHub

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

Jump to bottom

Use kubectl in EjsonSecretProvisioner #91

Merged
merged 2 commits into from
May 9, 2017
Merged

Use kubectl in EjsonSecretProvisioner #91

merged 2 commits into from
May 9, 2017

Commits on May 8, 2017

  1. Define the KubectlError

    @KnVerey
    KnVerey committed May 8, 2017
    Configuration menu
    Copy the full SHA
    40d0681 View commit details
    Browse the repository at this point in the history

Commits on May 9, 2017

  1. Use kubectl instead of kubeclient for the secret provisioner 

    We're having auth problems with kubeclient on some clusters, and deploys did not depend on that gem until the provisioner was introduced. We still would prefer to use kubeclient for this in the long run.
    @KnVerey
    KnVerey committed May 9, 2017
    Configuration menu
    Copy the full SHA
    3bb6ad7 View commit details
    Browse the repository at this point in the history