Remove Namespace from the JobSet Config

[andreyvelich]

What type of PR is this?

I removed namespace from the JobSet config as we discussed here: #719 (comment)

/kind cleanup
/assign @kannon92 @ahg-g @danielvegamyhre @tenzen-y

What this PR does / why we need it:

The webhook and JobSet controller always have the same namespace, so user should not override this value in the Config.
The namespace is taken from the Pod's service account: /var/run/secrets/kubernetes.io/serviceaccount/namespace

Which issue(s) this PR fixes:

Fixes # #720

Special notes for your reviewer:

Does this PR introduce a user-facing change?

The namespace parameter has been removed from the JobSet manager config.

[k8s-ci-robot]

Hi @andreyvelich. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[netlify]

✅ Deploy Preview for kubernetes-sigs-jobset canceled.

Name	Link
🔨 Latest commit	ace0065
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-jobset/deploys/678697c3dcc8c50008b33170

[kannon92]

/ok-to-test

[kannon92]

/assign @ahg-g

We probably should not drop fields from an API without a deprecation process.

I would add a release-note saying that we are dropping this at least.

[kannon92]

/hold

I want to wait for comments from @danielvegamyhre and @ahg-g.

[ahg-g]

Since this is an alpha API, we can technically change it. While I am ok with doing that for component config API, I think for the JobSet api itself we certainly need a stronger deprecation process where we support both v1alpha2 and v1 at the same time (assuming we go directly to v1)

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, andreyvelich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahg-g]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tenzen-y]

/lgtm

[kannon92]

/hold cancel