[Improvement][Deployment] Use minio as defaut storage if deployed in k8s

[EricGao888]

Purpose of the pull request

• Set minio as DS default storage when deployed in K8S, in this way, users could use resource center out-of-the-box.

Brief change log

• Already described above.

Verify this pull request

• Verified manually.

[EricGao888]

Seems the version and app version of DS helm chart is still 3.1.0. Should we change it to 3.1.3? cc @zhongjiajie

dolphinscheduler/deploy/kubernetes/dolphinscheduler/Chart.yaml

Lines 34 to 43 in dd0d730

	type: application
	# This is the chart version. This version number should be incremented each time you make changes
	# to the chart and its templates, including the app version.
	version: 3.1.0
	# This is the version number of the application being deployed. This version number should be
	# incremented each time you make changes to the application.
	appVersion: 3.1.0

[zhongjiajie]

Seems the version and app version of DS helm chart is still 3.1.0. Should we change it to 3.1.3? cc @zhongjiajie

dolphinscheduler/deploy/kubernetes/dolphinscheduler/Chart.yaml

Lines 34 to 43 in dd0d730

	type: application
	# This is the chart version. This version number should be incremented each time you make changes
	# to the chart and its templates, including the app version.
	version: 3.1.0
	# This is the version number of the application being deployed. This version number should be
	# incremented each time you make changes to the application.
	appVersion: 3.1.0

good catch, I think we should change to the latest version, could you please also change our release docs to tell release manager change it during the release process?

[EricGao888]

Seems the version and app version of DS helm chart is still 3.1.0. Should we change it to 3.1.3? cc @zhongjiajie

dolphinscheduler/deploy/kubernetes/dolphinscheduler/Chart.yaml

Lines 34 to 43 in dd0d730

	type: application
	# This is the chart version. This version number should be incremented each time you make changes
	# to the chart and its templates, including the app version.
	version: 3.1.0
	# This is the version number of the application being deployed. This version number should be
	# incremented each time you make changes to the application.
	appVersion: 3.1.0

good catch, I think we should change to the latest version, could you please also change our release docs to tell release manager change it during the release process?

Sure, will do : )

[zhongjiajie]

BTW, find flake dead link https://codecov.io/gh/apache/dolphinscheduler/branch/dev, could you also change url to https://app.codecov.io/gh/apache/dolphinscheduler/tree/dev?

[EricGao888]

BTW, find flake dead link https://codecov.io/gh/apache/dolphinscheduler/branch/dev, could you also change url to https://app.codecov.io/gh/apache/dolphinscheduler/tree/dev?

Sure, will fix it in this PR.

[kezhenxu94]

This reminds me we should also update the release doc to help release manager to also publish the helm chart so that users don't need to download the source codes in order to deploy with Helm Chart. FYI the helm chart repo is here https://hub.docker.com/r/apache/dolphinscheduler-helm/tags

Let me write up the release doc to include guide how to release the Helm Chart.

[zhongjiajie]

This reminds me we should also update the release doc to help release manager to also publish the helm chart so that users don't need to download the source codes in order to deploy with Helm Chart. FYI the helm chart repo is here https://hub.docker.com/r/apache/dolphinscheduler-helm/tags

Let me write up the release doc to include guide how to release the Helm Chart.

is there any guide about how to release helm chart to docker hub?

[kezhenxu94]

This reminds me we should also update the release doc to help release manager to also publish the helm chart so that users don't need to download the source codes in order to deploy with Helm Chart. FYI the helm chart repo is here https://hub.docker.com/r/apache/dolphinscheduler-helm/tags
Let me write up the release doc to include guide how to release the Helm Chart.

is there any guide about how to release helm chart to docker hub?

Check this #13385

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[zhongjiajie]

others LGTM

[zhongjiajie]

I am not sure whether the latest tag work here or not, I think there are some cases chart.yaml in dev branch not work in our latest version? @kezhenxu94 do you have time to take a look?