namespace is specified only as default.

[196Ikuchil]

Problem

In near future, we (maybe) merge PR #111.
In that PR, we will be able to import a variety of resources from external.

Therefore, we should change the logic so that we can import from different namespace.

kube-scheduler-simulator/pod/pod.go

Line 27 in ba06325

defaultNamespaceName = "default"

Example

We can check it after we merged #111. (Maybe)

# pod_namespace_test.yml
apiVersion: v1
kind: Pod
metadata:
  name: mypod
  namespace: test
  labels:
    name: mypod
spec:
  containers:
  - name: mypod
    image: nginx

Make a pod.

kubectl create namespace test
vim pod_namespace_test.yml
kubectl apply -f pod_namespace_test.yml
kubectl get pods --namespace=test

Start simulator

export EXTERNAL_IMPORT_ENABLED=1
make start

[sanposhiho]

Totally make sense. Please feel free to work on it if you are interested in :)

[196Ikuchil]

Relates #84

[sanposhiho]

/kind feature
/kind bug

[sanposhiho]

/priority important-soon

[196Ikuchil]

Hi, @sanposhiho
I'll work on this.
Since in the WebUI calls the apiserver directly, in this issue, I should implement it only on the function of importing the existing cluster?

/assign

[sanposhiho]

/reopen

We need to import namespace as well for this.

[k8s-ci-robot]

@sanposhiho: Reopened this issue.

In response to this:

/reopen

We need to import namespace.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sanposhiho]

/triage accepted
Not to mark as stale.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The issue has been marked as an important bug and triaged.
Such issues are automatically marked as frozen when hitting the rotten state
to avoid missing important bugs.

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle frozen

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted