fix: helm chart service label indentation issues

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,33 @@
+---
+name: Bug Report
+about: Report a bug encountered while using HAMi.
+labels: kind/bug
+
+---
+
+<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
+-->
+
+**What happened**:
+
+**What you expected to happen**:
+
+**How to reproduce it (as minimally and precisely as possible)**:
+
+**Anything else we need to know?**:
+
+- The output of `nvidia-smi -a` on your host
+- Your docker or containerd configuration file (e.g: `/etc/docker/daemon.json`)
+- The hami-device-plugin container logs
+- The hami-scheduler container logs
+- The kubelet logs on the node (e.g: `sudo journalctl -r -u kubelet`)
+- Any relevant kernel output lines from `dmesg`
+
+**Environment**:
+- HAMi version:
+- nvidia driver or other AI device driver version:
+- Docker version from `docker version`
+- Docker command, image and tag used
+- Kernel version from `uname -a`
+- Others:
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,4 @@
+contact_links:
+  - name: FAQ
+    url: https://github.com/Project-HAMi/HAMi/issues/646
+    about: Frequently asked questions and common solutions.

.github/ISSUE_TEMPLATE/enhancement.md

@@ -0,0 +1,22 @@
+---
+name: Enhancement Request
+about: Suggest an enhancement to the project
+labels: kind/feature
+
+---
+<!-- Please only use this template for submitting enhancement requests -->
+
+**What would you like to be added**:
+
+**What type of PR is this?**
+
+/kind feature
+
+**What this PR does / why we need it**:
+
+**Which issue(s) this PR fixes**:
+Fixes #
+
+**Special notes for your reviewer**:
+
+**Does this PR introduce a user-facing change?**:

.github/ISSUE_TEMPLATE/good-first.md

@@ -0,0 +1,31 @@
+---
+name: Good First Issue
+about: Publish a good first issue
+labels: good first issue
+
+---
+
+<!-- Please use this template while publishing a good first issue. Thanks!
+-->
+
+**Task description**:
+
+**Solution**:
+
+**Who can join or take the task**:
+
+The good first issue is intended for `first-time contributors` to get started on his/her contributor journey.
+
+After a contributor has successfully completed 1-2 good first issue's,
+they should be ready to move on to `help wanted` items, saving the remaining `good first issue` for other new contributors.
+
+**How to join or take the task**:
+
+Just reply on the issue with the message `/assign` in a separate line.
+
+Then, the issue will be assigned to you.
+
+**How to ask for help**:
+
+If you need help or have questions, please feel free to ask on this issue.
+The issue author or other members of the community will guide you through the contribution process.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,15 @@
+---
+name: Question
+about: Question relating to HAMi.
+labels: kind/question
+
+---
+
+**Please provide an in-depth description of the question you have**:
+
+**What do you think about this question?**:
+
+**Environment**:
+- HAMi version:
+- Kubernetes version:
+- Others:

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+**What type of PR is this?**
+
+<!--
+Add one of the following kinds:
+/kind bug
+/kind cleanup
+/kind deprecation
+/kind design
+/kind documentation
+/kind failing-test
+/kind feature
+/kind flake
+-->
+
+**What this PR does / why we need it**:
+
+**Which issue(s) this PR fixes**:
+Fixes #
+
+**Special notes for your reviewer**:
+
+**Does this PR introduce a user-facing change?**:

.github/dependabot.yml

@@ -0,0 +1,21 @@
+
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+
+version: 2
+updates:
+  - package-ecosystem: "gomod"
+    directory: "/"
+    schedule:
+      interval: "daily"
+  - package-ecosystem: "docker"
+    directory: "/docker"
+    schedule:
+      interval: "daily"
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily" 

.github/release.yml

@@ -0,0 +1,29 @@
+# .github/release.yml
+changelog:
+  exclude:
+    labels:
+    - ignore-for-release
+    - github-actions
+    authors:
+    - dependabot[bot]
+  categories:
+  - title: ✨ New Features
+    labels:
+    - feature
+    - design
+    - enhancement
+  - title: 🐛 Bug Fixes
+    labels:
+    - bug
+  - title: 📚 Documentation
+    labels:
+    - documentation
+  - title: ⬆️ Dependencies
+    labels:
+    - dependencies
+  - title: 💥 Breaking Changes
+    labels:
+    - breaking-change
+  - title: 🔨 Other Changes
+    labels:
+    - "*"

.github/workflows/auto-release.yaml

@@ -0,0 +1,144 @@
+name: 1.Release
+
+# it is trigger by tag event:
+# 1 build the release image, push images to ghcr.io, and build image like: ghcr.io/xxxx:v1.0.0
+# 2 package the chart package, update index.yaml and commit to '/charts' of branch 'github_pages' ( PR with label pr/release/robot_update_githubpage )
+# 3 create changelog file, commit to '/changelogs' of branch 'github_pages' for githubPage ( PR with label pr/release/robot_update_githubpage )
+# 4 commit '/docs' to '/docs' of branch 'github_pages'
+# 5 create a release , attached with the chart and changelog
+
+on:
+  release:
+    types:
+    - prereleased
+  push:
+    tags:
+      - v[0-9]+.[0-9]+.[0-9]+
+      - v[0-9]+.[0-9]+.[0-9]+-rc[0-9]+
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Tag'
+        required: true
+        default: v1.0.0
+permissions: write-all
+
+jobs:
+  pre-release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    outputs:
+      tag: ${{ env.RUN_TAG }}
+    steps:
+    - name: Check Version
+      run: |
+        TagVersion="${{ env.RUN_TAG }}"
+        RecordVersion=` cat VERSION  | tr -d ' ' | tr -d '\n' `
+        if [ "$RecordVersion" != "$TagVersion" ] ; then
+          echo "error, version $RecordVersion of '/VERSION' is different with Tag $TagVersion "
+          exit 1
+        fi
+        #no need to check chart version, which will auto update to /VERSION by CI
+      # generate release notes for the new release branch
+    - name: Generate pre release notes
+      if: startsWith(github.ref, 'refs/tags/')
+      uses: softprops/action-gh-release@v2
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        prerelease: true
+        generate_release_notes: true
+
+  ensure-tag:
+    runs-on: ubuntu-latest
+    needs: pre-release
+    outputs:
+      tag: ${{ env.RUN_TAG }}
+    steps:
+      - name: Free disk space
+        # https://github.com/actions/virtual-environments/issues/709
+        run: |
+          echo "=========original CI disk space"
+          df -h
+          sudo rm -rf "/usr/local/share/boost"
+          sudo rm -rf "$AGENT_TOOLSDIRECTORY"
+          echo "=========after clean up, the left CI disk space"
+          df -h
+      - name: Get Ref
+        id: get_ref
+        run: |
+          if ${{ github.event_name == 'workflow_dispatch' }} ; then
+            echo "call by self workflow_dispatch"
+            echo "RUN_TAG=${{ github.event.inputs.tag }}" >> $GITHUB_ENV
+            YBranchName=` grep -Eo "v[0-9]+\.[0-9]+" <<< "${{ github.event.inputs.tag }}" `
+          elif ${{ github.event_name == 'push' }} ; then
+            echo "call by push tag"
+            echo "RUN_TAG=${GITHUB_REF##*/}" >> $GITHUB_ENV
+            YBranchName=` grep -Eo "v[0-9]+\.[0-9]+" <<< "${GITHUB_REF##*/}" `
+          else
+            echo "unexpected event: ${{ github.event_name }}"
+            exit 1
+          fi
+          echo "YBranchName=${YBranchName}"
+          if [ -n "$YBranchName" ] ; then
+              echo "RUN_YBranchName=${YBranchName}" >> $GITHUB_ENV
+          else
+              echo "error, failed to find y branch"
+              exit 1
+          fi
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ env.RUN_TAG }}
+        # if branch exists, the action will no fail, and it output created=false
+      - name: release Y branch
+        uses: peterjgrainger/action-create-branch@v3.0.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          branch: 'release-${{ env.RUN_YBranchName }}'
+          sha: '${{ github.sha }}'
+
+
+  release-image:
+    needs: ensure-tag
+    uses: ./.github/workflows/call-release-image.yaml
+    with:
+      ref: ${{ needs.ensure-tag.outputs.tag }}
+    secrets: inherit
+
+  release-chart:
+    needs: [ensure-tag]
+    uses: ./.github/workflows/call-release-helm.yaml
+    with:
+      ref: ${{ needs.ensure-tag.outputs.tag }}
+      submit: true
+    secrets: inherit
+
+  # generate changelog and update to github releases pages
+  release-notes:
+    needs: [release-chart,release-image]
+    uses: ./.github/workflows/call-release-notes.yaml
+    with:
+      ref: ${{ needs.ensure-tag.outputs.tag }}
+
+  release-website:
+    needs: [release-notes]
+    uses: ./.github/workflows/call-release-website.yaml
+    with:
+      ref: ${{ needs.ensure-tag.outputs.tag }}
+  # excute a full e2e test when hami release
+  release-e2e:
+    needs: [release-notes]
+    uses: ./.github/workflows/call-e2e.yaml
+    with:
+      ref: ${{ needs.ensure-tag.outputs.tag }}
+
+  # excute a compatibility test when hami release
+  release-e2e-upgrade:
+      needs: [release-notes]
+      uses: ./.github/workflows/call-e2e-upgrade.yaml
+      with:
+        ref: ${{ needs.ensure-tag.outputs.tag }}
+

.github/workflows/call-e2e-upgrade.yaml

@@ -0,0 +1,18 @@
+name: Call e2e upgrade test
+
+on:
+  workflow_call:
+    inputs:
+      ref:
+        required: true
+        type: string
+permissions: write-all
+
+jobs:
+  upgrade-e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - name: e2e upgrade test
+        # https://github.com/actions/virtual-environments/issues/709
+        run: |
+          echo "Need to add e2e upgrade test"

.github/workflows/call-e2e.yaml

@@ -0,0 +1,18 @@
+name: Call e2e test
+
+on:
+  workflow_call:
+    inputs:
+      ref:
+        required: true
+        type: string
+permissions: write-all
+
+jobs:
+  e2e:
+    runs-on: ubuntu-latest
+    steps:
+      - name: e2e test
+        # https://github.com/actions/virtual-environments/issues/709
+        run: |
+          echo "Need to add e2e test"