We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
What did you do?
scorecard-test
~/.kube/config
operator-sdk alpha scorecard ./internal/scorecard/alpha/testdata/bundle --skip-cleanup
kubectl get pods
What did you expect to see? I expected to see the scorecard pods in the scorecard-test namespace.
What did you see instead? Under which circumstances? I found the scorecard pods in the default namespace.
default
Environment
operator-sdk version: "v0.19.0-17-g2594430b", commit: "2594430b796836fb2e1b1b79b5970beae5346a37", kubernetes version: "v1.18.2", go version: "go1.14.4 linux/amd64"
go version go1.13.10 linux/amd64
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes cluster kind: minikube
Are you writing your operator in ansible, helm, or go? N/A
Possible Solution When loading the config, get the current context's namespace and use that as the default when --namespace is not defined.
--namespace
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
jmccormick2001
Successfully merging a pull request may close this issue.
Bug Report
What did you do?
scorecard-test
~/.kube/config
file to makescorecard-test
my current context namespaceoperator-sdk alpha scorecard ./internal/scorecard/alpha/testdata/bundle --skip-cleanup
kubectl get pods
What did you expect to see?
I expected to see the scorecard pods in the
scorecard-test
namespace.What did you see instead? Under which circumstances?
I found the scorecard pods in the
default
namespace.Environment
operator-sdk version: "v0.19.0-17-g2594430b", commit: "2594430b796836fb2e1b1b79b5970beae5346a37", kubernetes version: "v1.18.2", go version: "go1.14.4 linux/amd64"
go version go1.13.10 linux/amd64
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.5", GitCommit:"e6503f8d8f769ace2f338794c914a96fc335df0f", GitTreeState:"clean", BuildDate:"2020-06-26T03:47:41Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:48:36Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes cluster kind: minikube
Are you writing your operator in ansible, helm, or go? N/A
Possible Solution
When loading the config, get the current context's namespace and use that as the default when
--namespace
is not defined.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: