[Improvement][K8S TASK] get namespace's information until execute

[fuchanghai]

Search before asking

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

Description

• store namespaceId when save process definition
• before run process instance ,according namespaceId get namespace name and other information

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[Radeity]

Hi @fuchanghai , I don't get your point, would you like to give some further explanation of this issue?

[fuchanghai]

Hi @fuchanghai , I don't get your point, would you like to give some further explanation of this issue?

hi @Radeity

Currently, the k8s node stores the namespace name. If you want to modify the name, the process definition associated with the namespace needs to be modified

[Radeity]

Hi @fuchanghai , I don't get your point, would you like to give some further explanation of this issue?

hi @Radeity

Currently, the k8s node stores the namespace name. If you want to modify the name, the process definition associated with the namespace needs to be modified

Oh, you mean namespace in k8s task's parameter. How about directly remove t_ds_k8s_namespace? cc @Gallardot

[Gallardot]

Oh, you mean namespace in k8s task's parameter. How about directly remove t_ds_k8s_namespace? cc @Gallardot

I think the solution described by @fuchanghai would be helpful in resolving this issue.

What does directly remove t_ds_k8s_namespace means ? @Radeity

[Radeity]

Oh, you mean namespace in k8s task's parameter. How about directly remove t_ds_k8s_namespace? cc @Gallardot

I think the solution described by @fuchanghai would be helpful in resolving this issue.

What does directly remove t_ds_k8s_namespace means ? @Radeity

I think we don't have to maintain this table and we can remove namespace management, since now we don't have the ability to manage namespace in k8s cluster. Thus, namespace is same with image in k8s task's parameters. Considering user-friendliness, maybe we can use project-level parameter to define these task parameter.

[Gallardot]

I think we don't have to maintain this table and we can remove namespace management, since now we don't have the ability to manage namespace in k8s cluster. Thus, namespace is same with image in k8s task's parameters. Considering user-friendliness, maybe we can use project-level parameter to define these task parameter.

But currently, the dolphinscheduler has the authority to manage namespaces, and specific dolphinscheduler users can use the namespace permissions of specific clusters, which is beneficial for both permission management and ease of use.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.