Skip to content

README.md fails to include a step to ensure KUBECONFIG is always set. #19

@sbates130272

Description

@sbates130272

Running some of the command line examples in the README.md fail. For example:

$ ./linux/run-k8s-job.sh ./example-templates/workloads/rocm-job-template.yaml dev
Deploying the Job in namespace 'dev'...
error: error validating "./example-templates/workloads/rocm-job-template.yaml": error validating data: failed to download openapi: Get "http://localhost:8080/openapi/v2?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false
$

This can be resolved by ensuring the environment variable KUBECONFIG is set in the current shell:

$ KUBECONFIG= ./linux/run-k8s-job.sh ./example-templates/workloads/rocm-job-template.yaml dev
<snip>
job.batch "rocm-test-job-stebates" deleted
Job execution completed successfully in 'dev' namespace.
$

It would be ideal if the README.md explicitly told the user how best to do this and ideally in a way that is persistent across sessions (e.g. in .bashrc).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions