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

fix: handle cases when running inside a kubernetes cluster #17

Merged
merged 2 commits into from
Aug 14, 2024
Merged

fix: handle cases when running inside a kubernetes cluster #17

merged 2 commits into from
Aug 14, 2024

Commits on Apr 2, 2024

  1. fix: handle cases when running inside a kubernetes cluster 

    The current setup for the plugin assumes that we have a kubeconfig file used to connect to the cluster. However, this is not the case if the code submitting the job is itself running in a pod in the cluster, as we will need to use the default service account provided by the cluster 
This modifies the init to catch any errors when loading a kubeconfig file and use the inlcuster configuration instead
    @bilalshaikh42
    bilalshaikh42 authored Apr 2, 2024
    Configuration menu
    Copy the full SHA
    4463df4 View commit details
    Browse the repository at this point in the history

  2. fix: include package name when calling config function

    @bilalshaikh42
    bilalshaikh42 authored Apr 2, 2024
    Configuration menu
    Copy the full SHA
    9b755d4 View commit details
    Browse the repository at this point in the history