Tags: KusionStack/charts
Tags
chart: bump kuperator to v0.6.2 (#118) <!-- Thank you for contributing to KusionStack! Note: 1. With pull requests: - Open your pull request against "main" - Your pull request should have no more than two commits, if not you should squash them. - It should pass all tests in the available continuous integration systems such as GitHub Actions. - You should add/modify tests to cover your proposed code changes. - If your pull request contains a new feature, please document it on the README. 2. Please create an issue first to describe the problem. We recommend that link the issue with the PR in the following question. For more info, check https://kusionstack.io/docs/governance/contribute/ --> #### 1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".): - [ ] N - [ ] Y <!-- You can add issue references here. e.g. fix #123, re #123, fix https://github.com/XXX/issues/44 --> #### 2. What is the scope of this PR (e.g. component or file name): <!-- You can add the scope of this change here. e.g. /src/server/core.rs, kusionstack/KCLVM/kclvm-parser --> #### 3. Provide a description of the PR(e.g. more details, effects, motivations or doc link): <!-- You can choose a brief description here --> - [ ] Affects user behaviors - [ ] Contains syntax changes - [ ] Contains variable changes - [ ] Contains experimental features - [ ] Performance regression: Consumes more CPU - [ ] Performance regression: Consumes more Memory - [ ] Other <!-- You can add more details here. e.g. Call method "XXXX" to ..... in order to ...., More details: https://XXXX.com/doc...... --> #### 4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link): - [ ] N - [ ] Y <!-- You can add more details here. e.g. Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be affected. More details: https://XXXX.com/doc...... --> #### 5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: <!-- You can choose a brief description here --> - [ ] Unit test - [ ] Integration test - [ ] Benchmark (add benchmark stats below) - [ ] Manual test (add detailed scripts or steps below) - [ ] Other <!-- You can add more details here. e.g. The test case in XXXX is used to ..... test cases in /src/tests/XXXXX test cases https://github.com/XXX/pull/44 benchmark stats: time XXX ms --> #### 6. Release note <!-- compatibility change, improvement, bugfix, and new feature need a release note --> Please refer to [Release Notes Language Style Guide](https://kusionstack.io/docs/governance/release-policy/) to write a quality release note. ```release-note None ```
chore(karpor): bump app version to 0.6.4, chart version to 0.7.6 (#117) This PR updates the Karpor Helm chart with the following changes: - Bump the `appVersion` to `0.6.4` - Bump the `version` to `0.7.6` These updates ensure that the chart reflects the latest Karpor release. **Note**: This PR was automatically generated by the **karpor-chart-updater[bot]**. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: bump version to 0.7.2 and update AI backend docs (#102) - Increment version in Chart.yaml from 0.7.1 to 0.7.2 - Update README.md and values.yaml to include detailed AI backend options This commit updates the project version and improves documentation clarity by listing available AI backend options, including OpenAI, Azure OpenAI, and Hugging Face. <!-- Thank you for contributing to KusionStack! Note: 1. With pull requests: - Open your pull request against "main" - Your pull request should have no more than two commits, if not you should squash them. - It should pass all tests in the available continuous integration systems such as GitHub Actions. - You should add/modify tests to cover your proposed code changes. - If your pull request contains a new feature, please document it on the README. 2. Please create an issue first to describe the problem. We recommend that link the issue with the PR in the following question. For more info, check https://kusionstack.io/docs/governance/contribute/ --> #### 1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".): - [ ] N - [ ] Y <!-- You can add issue references here. e.g. fix #123, re #123, fix https://github.com/XXX/issues/44 --> #### 2. What is the scope of this PR (e.g. component or file name): <!-- You can add the scope of this change here. e.g. /src/server/core.rs, kusionstack/KCLVM/kclvm-parser --> #### 3. Provide a description of the PR(e.g. more details, effects, motivations or doc link): <!-- You can choose a brief description here --> - [ ] Affects user behaviors - [ ] Contains syntax changes - [ ] Contains variable changes - [ ] Contains experimental features - [ ] Performance regression: Consumes more CPU - [ ] Performance regression: Consumes more Memory - [ ] Other <!-- You can add more details here. e.g. Call method "XXXX" to ..... in order to ...., More details: https://XXXX.com/doc...... --> #### 4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link): - [ ] N - [ ] Y <!-- You can add more details here. e.g. Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be affected. More details: https://XXXX.com/doc...... --> #### 5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: <!-- You can choose a brief description here --> - [ ] Unit test - [ ] Integration test - [ ] Benchmark (add benchmark stats below) - [ ] Manual test (add detailed scripts or steps below) - [ ] Other <!-- You can add more details here. e.g. The test case in XXXX is used to ..... test cases in /src/tests/XXXXX test cases https://github.com/XXX/pull/44 benchmark stats: time XXX ms --> #### 6. Release note <!-- compatibility change, improvement, bugfix, and new feature need a release note --> Please refer to [Release Notes Language Style Guide](https://kusionstack.io/docs/governance/release-policy/) to write a quality release note. ```release-note None ```
fix secret labels typo "labesl" (#100) fix typo : secret label bug <!-- Thank you for contributing to KusionStack! Note: 1. With pull requests: - Open your pull request against "main" - Your pull request should have no more than two commits, if not you should squash them. - It should pass all tests in the available continuous integration systems such as GitHub Actions. - You should add/modify tests to cover your proposed code changes. - If your pull request contains a new feature, please document it on the README. 2. Please create an issue first to describe the problem. We recommend that link the issue with the PR in the following question. For more info, check https://kusionstack.io/docs/governance/contribute/ --> #### 1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".): - [x] N - [ ] Y <!-- You can add issue references here. e.g. fix #123, re #123, fix https://github.com/XXX/issues/44 --> #### 2. What is the scope of this PR (e.g. component or file name): charts/charts/karpor/templates/karpor-server.yml:19 <!-- You can add the scope of this change here. e.g. /src/server/core.rs, kusionstack/KCLVM/kclvm-parser --> #### 3. Provide a description of the PR(e.g. more details, effects, motivations or doc link): bug fix ```yaml apiVersion: v1 kind: Secret metadata: name: karpor-auth namespace: {{ .Values.namespace }} labesl: {{- include "karpor.labels" (dict "context" . "component" .Values.server.name) | nindent 4 }} ``` The label field is wrong, and the label of the Secret control through Values.yaml will not take effect! <!-- You can choose a brief description here --> - [x] Affects user behaviors - [ ] Contains syntax changes - [ ] Contains variable changes - [ ] Contains experimental features - [ ] Performance regression: Consumes more CPU - [ ] Performance regression: Consumes more Memory - [ ] Other <!-- You can add more details here. e.g. Call method "XXXX" to ..... in order to ...., More details: https://XXXX.com/doc...... --> #### 4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link): - [x] N - [ ] Y <!-- You can add more details here. e.g. Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be affected. More details: https://XXXX.com/doc...... --> #### 5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: <!-- You can choose a brief description here --> - [ ] Unit test - [ ] Integration test - [ ] Benchmark (add benchmark stats below) - [ ] Manual test (add detailed scripts or steps below) - [ ] Other <!-- You can add more details here. e.g. The test case in XXXX is used to ..... test cases in /src/tests/XXXXX test cases https://github.com/XXX/pull/44 benchmark stats: time XXX ms --> #### 6. Release note <!-- compatibility change, improvement, bugfix, and new feature need a release note --> Please refer to [Release Notes Language Style Guide](https://kusionstack.io/docs/governance/release-policy/) to write a quality release note. ```release-note None ```
feat: update kubeconfig configuration format in kusion (#97) <!-- Thank you for contributing to KusionStack! Note: 1. With pull requests: - Open your pull request against "main" - Your pull request should have no more than two commits, if not you should squash them. - It should pass all tests in the available continuous integration systems such as GitHub Actions. - You should add/modify tests to cover your proposed code changes. - If your pull request contains a new feature, please document it on the README. 2. Please create an issue first to describe the problem. We recommend that link the issue with the PR in the following question. For more info, check https://kusionstack.io/docs/governance/contribute/ --> #### 1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".): - [X] N - [ ] Y <!-- You can add issue references here. e.g. fix #123, re #123, fix https://github.com/XXX/issues/44 --> #### 2. What is the scope of this PR (e.g. component or file name): charts/kusion scripts/install-kusion.sh <!-- You can add the scope of this change here. e.g. /src/server/core.rs, kusionstack/KCLVM/kclvm-parser --> #### 3. Provide a description of the PR(e.g. more details, effects, motivations or doc link): - add a script to install kusion - update kubeconfig configuration format in values.yaml to support easier installation - bump appversion and chart version to sync kusion's version - update doc - add kubeconfig configuration part and update installation instructions <!-- You can choose a brief description here --> - [X] Affects user behaviors - [ ] Contains syntax changes - [X] Contains variable changes - [ ] Contains experimental features - [ ] Performance regression: Consumes more CPU - [ ] Performance regression: Consumes more Memory - [X] Other <!-- You can add more details here. e.g. Call method "XXXX" to ..... in order to ...., More details: https://XXXX.com/doc...... --> #### 4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link): - [ ] N - [X] Y <!-- You can add more details here. e.g. Calling method "XXXX" will cause the "XXXX", "XXXX" modules to be affected. More details: https://XXXX.com/doc...... --> #### 5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links: <!-- You can choose a brief description here --> - [ ] Unit test - [ ] Integration test - [ ] Benchmark (add benchmark stats below) - [X] Manual test (add detailed scripts or steps below) - [ ] Other <!-- You can add more details here. e.g. The test case in XXXX is used to ..... test cases in /src/tests/XXXXX test cases https://github.com/XXX/pull/44 benchmark stats: time XXX ms --> #### 6. Release note <!-- compatibility change, improvement, bugfix, and new feature need a release note --> Please refer to [Release Notes Language Style Guide](https://kusionstack.io/docs/governance/release-policy/) to write a quality release note. ```release-note None ```
PreviousNext