[Bug] [TASK_K8S] Unable to select k8s namespace

[youzif]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Hi bro.
When I want to use k8s as a workflow, I find that there is no namespace to choose from. Does this mean that I cannot choose which k8s cluster or namespace to run this task in?

The picture below is a screenshot of my ds

The picture below is a screenshot of the ds official document

and Here are some error reports for tasks:

Version

3.2.2

Replenish

Cluster and namespace have been configured in DS

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[SbloodyS]

PTAL, Thanks. @Gallardot

[youzif]

I encountered the same issue while setting up a test environment with version 3.2.2. Initially, when I had not created any clusters or namespaces in DS, there was an option to select a namespace when creating a new workflow. However, after creating clusters and namespaces in DS, the namespace option disappeared when creating a new workflow.

did you find any solution?

[youzif]

According to the task execution, in fact, the namespace is not obtained.

[youzif]

@Gallardot could you provide some help？

[e7868a]

I discovered the reason in the code. To create a K8S-type task, you need to create a K8S-type data source within the "Datasource" section, rather than using the "K8S Namespace manage" option under "Security". However, in the UI code for version 3.2.2 (#16214), the K8S-type data source option has been removed, so it's not possible to create a K8S-type data source in this version.

[youzif]

I discovered the reason in the code. To create a K8S-type task, you need to create a K8S-type data source within the "Datasource" section, rather than using the "K8S Namespace manage" option under "Security". However, in the UI code for version 3.2.2 (#16214), the K8S-type data source option has been removed, so it's not possible to create a K8S-type data source in this version.

I think you are right, looking forward to fixing this in the new version

[SbloodyS]

Fixed in dev branch.