[pull] main from labring:main

.chglog/CHANGELOG.tpl.md

@@ -0,0 +1,46 @@
+{{ range .Versions }}
+# Welcome to the {{ .Tag.Name }} release of Sealos!🎉🎉!
+
+<a name="{{ .Tag.Name }}"></a>
+## {{ if .Tag.Previous }}[{{ .Tag.Name }}]({{ $.Info.RepositoryURL }}/compare/{{ .Tag.Previous.Name }}...{{ .Tag.Name }}){{ else }}{{ .Tag.Name }}{{ end }} ({{ datetime "2006-01-02" .Tag.Date }})
+
+{{ range .CommitGroups -}}
+### {{ .Title }}
+
+{{ range .Commits -}}
+* {{ if .Scope }}**{{ .Scope }}:** {{ end }}{{ .Subject }}
+{{ end }}
+{{ end -}}
+
+{{- if .RevertCommits -}}
+### Reverts
+
+{{ range .RevertCommits -}}
+* {{ .Revert.Header }}
+{{ end }}
+{{ end -}}
+
+{{- if .MergeCommits -}}
+### Pull Requests
+
+{{ range .MergeCommits -}}
+* {{ .Header }}
+{{ end }}
+{{ end -}}
+
+{{- if .NoteGroups -}}
+{{ range .NoteGroups -}}
+### {{ .Title }}
+
+{{ range .Notes }}
+{{ .Body }}
+{{ end }}
+{{ end -}}
+{{ end -}}
+{{ end -}}
+
+See [the CHANGELOG](https://github.com/labring/sealos/blob/main/CHANGELOG/CHANGELOG.md) for more details.
+
+Your patronage towards Sealos is greatly appreciated 🎉🎉.
+
+If you encounter any problems during its usage, please create an issue in the [GitHub repository](https://github.com/labring/sealos), we're committed to resolving your problem as soon as possible.

.chglog/config.yml

@@ -0,0 +1,33 @@
+style: github
+template: CHANGELOG.tpl.md
+info:
+  title: CHANGELOG
+  repository_url: https://github.com/labring/sealos
+options:
+  tag_filter_pattern: '^v'
+  sort: "date"
+  commits:
+   sort_by: Type
+   filters:
+     Type:
+       - feat
+       - fix
+       - perf
+       - refactor
+  commit_groups:
+    group_by: Type
+    sort_by: Title
+    title_maps:
+      feat: New Features
+      fix: Bug Fixes
+      perf: Performance Improvements
+      refactor: Code Refactoring
+  header:
+    pattern: '^(\w*)(?:\(([\w$.\-*/ ]*)\))?: (.*)$'
+    pattern_maps:
+      - Type
+      - Scope
+      - Subject
+  notes:
+    keywords:
+      - BREAKING CHANGE

.devcontainer/Dockerfile

@@ -0,0 +1,24 @@
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.238.1/containers/go/.devcontainer/base.Dockerfile
+
+# [Choice] Go version (use -bullseye variants on local arm64/Apple Silicon): 1, 1.16, 1.17, 1-bullseye, 1.16-bullseye, 1.17-bullseye, 1-buster, 1.16-buster, 1.17-buster
+ARG VARIANT="1-bullseye"
+FROM mcr.microsoft.com/vscode/devcontainers/go:0-${VARIANT}
+
+# [Choice] Node.js version: none, lts/*, 16, 14, 12, 10
+ARG NODE_VERSION="none"
+RUN if [ "${NODE_VERSION}" != "none" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+    && apt-get -y install --no-install-recommends libgpgme-dev libbtrfs-dev libdevmapper-dev
+
+# [Optional] Uncomment the next lines to use go get to install anything else you need
+USER vscode
+RUN go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest \
+    && go install golang.org/x/tools/cmd/goimports@latest \
+    && go install github.com/google/addlicense@latest \
+    && go install k8s.io/code-generator/cmd/deepcopy-gen@latest \
+    && go install k8s.io/code-generator/cmd/conversion-gen@latest
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1

.devcontainer/devcontainer.json

@@ -0,0 +1,48 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.238.1/containers/go
+{
+	"name": "Go",
+	"build": {
+		"dockerfile": "Dockerfile",
+		"args": {
+			// Update the VARIANT arg to pick a version of Go: 1, 1.18, 1.17
+			// Append -bullseye or -buster to pin to an OS version.
+			// Use -bullseye variants on local arm64/Apple Silicon.
+			"VARIANT": "1-bullseye",
+			// Options
+			"NODE_VERSION": "lts/*"
+		}
+	},
+	"runArgs": [ "--cap-add=SYS_PTRACE", "--security-opt", "seccomp=unconfined" ],
+
+	// Configure tool-specific properties.
+	"customizations": {
+		// Configure properties specific to VS Code.
+		"vscode": {
+			// Set *default* container specific settings.json values on container create.
+			"settings": {
+				"go.toolsManagement.checkForUpdates": "local",
+				"go.useLanguageServer": true,
+				"go.gopath": "/go"
+			},
+
+			// Add the IDs of extensions you want installed when the container is created.
+			"extensions": [
+				"golang.Go"
+			]
+		}
+	},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "go version",
+
+	// Comment out to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+	"remoteUser": "vscode",
+	"features": {
+		"docker-in-docker": "latest",
+		"kubectl-helm-minikube": "latest"
+	}
+}

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,60 @@
+name: 🐞 Sealos Bug report
+description: Create a report to help us improve
+title: 'BUG: brief description of the bug'
+labels: kind/bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting an issue. 
+
+        Please fill in as much of the following form as you're able.
+  - type: input
+    attributes:
+      label: Sealos Version
+      description: Sealos Version of your installtion
+      placeholder: eg. v4.1.3
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: How to reproduce the bug?
+      description: Enter details about your bug.
+      placeholder: |
+        1. In this environment...
+        2. With this config...
+        3. Run '...'
+        4. See error...
+  - type: textarea
+    attributes:
+      label: What is the expected behavior?
+      description: If possible please provide textual output instead of screenshots.
+  - type: textarea
+    attributes:
+      label: What do you see instead?
+      description: If possible please provide textual output instead of screenshots.
+  - type: textarea
+    attributes:
+      label: Operating environment
+      description: |
+        examples:
+          - **Sealos version**: eg. v4.1.3
+          - **Docker version**:   eg. v20.10.7
+          - **Kubernetes version**: eg. v1.25.0
+          - **Operating system**: eg. centos7
+          - **Runtime environment**:  eg. physical machine (100G memory, 10 core cpu, 10T storage), virtual machine (virbox, 10G memory, 2 core cpu, 100G storage), cloud(aws, 10G memory, 2 core cpu, 100G storage)
+          - **Cluster size**: eg 3 master, 3 node
+          - **Additional information**: istio, dashboard ...
+      value: |
+          - Sealos version:
+          - Docker version:
+          - Kubernetes version:
+          - Operating system:
+          - Runtime environment:
+          - Cluster size:
+          - Additional information:
+      render: markdown
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Tell us anything else you think we should know.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,12 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Ask a question (GitHub Discussions)
+    url: https://github.com/labring/sealos/discussions
+    about: |
+      Please do not submit "a bug report" for asking a question.
+      In most cases, GitHub Discussions is the best place to ask a question.
+      If you are not sure whether you are going to report a bug or ask a question,
+      please consider asking in GitHub Discussions first.
+  - name: Join Our Discord
+    url: https://discord.gg/eHyXHtSE
+    about: Join our community, we will keep you in the loop.

.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,34 @@
+name: 📝 Documentation Suggestion
+description: Suggest an improvement or addition to the official documentation
+title: 'Docs: brief description of your suggestion'
+labels: kind/documentation
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for making a suggestion to improve our documentation. 
+
+        Please fill in as much of the following form as you're able.
+  - type: input
+    attributes:
+      label: Documentation Section
+      description: The section of the documentation where your suggestion applies.
+      placeholder: eg. Installation Guide
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What is the current documentation state?
+      description: Briefly describe the current state of the section.
+  - type: textarea
+    attributes:
+      label: What is your suggestion?
+      description: Please describe your suggestion for improving or adding to the documentation.
+  - type: textarea
+    attributes:
+      label: Why is this change beneficial?
+      description: Explain why you believe your suggestion will improve the documentation.
+  - type: textarea
+    attributes:
+      label: Additional information
+      description: Provide any other details or context that might be helpful for us to understand your suggestion.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,20 @@
+name: "\U0001F680 Sealos feature request"
+description: Suggest an idea for this project
+labels: kind/feature
+title: 'Feature: brief description of the feature'
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for suggesting an idea to improve Sealos.
+        Please fill in as much of the following form as you're able.
+  - type: textarea
+    attributes:
+      label: What is the problem this feature will solve?
+  - type: textarea
+    attributes:
+      label: If you have solution，please describe it
+      description: Describe the requests. If you already have something in mind... PRs are welcome!
+  - type: textarea
+    attributes:
+      label: What alternatives have you considered?

.github/PULL_REQUEST_TEMPLATE.md

@@ -1 +1,6 @@
-[SKIP CI]sealos: 一句话简短描述该 PR 内容
+<!-- 
+If you are developing a feature, please provide documentation.
+If you are solving a bug, please associate the corresponding issue.
+Please standardize the title and introduction information of the PR, 
+because it will be placed in the release note.
+-->