Release notes 0.9.x #1113
Release notes 0.9.x #1113
Conversation
Path: "Documenttion/Chaos engineering/release-notes/chaos-engineering" URL: Signed-off-by: Smriti S <smriti.satyanarayana@harness.io>
SmritiSatya
added
Release notes
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
release-notes/chaos-engineering.md
Outdated
| ### What’s new | ||
|
|
||
| * New access control **Execute** to execute chaos experiments (CHAOS-1311) | ||
| * This release adds a new access control, **Execute**, in addition to **View**, **Create/Edit**, and **Delete**. **Execute** allows you to execute the chaos experiments, whereas **Create/Edit** will only allow you to create a chaos experiment or edit an existing chaos experiment. The newly added access control provides granularity while working with chaos experiments. |
There was a problem hiding this comment.
Suggestion. ...The Execute access control allows you to...
There was a problem hiding this comment.
Hi @SmritiSatya can we remove this point for this release, For this to work completely, one more change is required. We can take this in next release.
release-notes/chaos-engineering.md
Outdated
|
|
||
|
|
||
| * Update button to see available updates for a chaos experiment (CHAOS-1069) | ||
| * This release displays an ‘Update’ button alongside the chaos experiment. When you click this button, it shows if an update is available for the experiment. |
|
|
||
|
|
||
| * Clicking an experiment goes to the experiment builder page (CHAOS-995) | ||
| * This release takes you to the **Experiment Builder** page when you click the chaos experiment, instead of showing the **Overview** page. This way, you can directly edit the chaos experiment, save it, and run it. |
There was a problem hiding this comment.
Starting this release, when you click the chaos experiment, it takes you to the Experiment Builder page instead of the Overview page.
release-notes/chaos-engineering.md
Outdated
|
|
||
|
|
||
| * Replica pods are deleted when a chaos infrastructure is disabled (CHAOS-1290) | ||
| * This release ensures that all replica pods, including the subscriber pod, are deleted when the chaos infrastructure is disabled. You can delete the pods from the user interface by clicking **Disable** which displays a set of commands you can execute on your terminal. The commands vary depending on the mode of deployment (cluster-mode or namespace-mode). |
There was a problem hiding this comment.
As a user I am interpreting this as the improvement is available only for this release. How about saying:
Starting/from this release, all replica pods, including the subscriber pod, are deleted when the chaos infrastructure is disabled.
release-notes/chaos-engineering.md
Outdated
| * This release ensures that all replica pods, including the subscriber pod, are deleted when the chaos infrastructure is disabled. You can delete the pods from the user interface by clicking **Disable** which displays a set of commands you can execute on your terminal. The commands vary depending on the mode of deployment (cluster-mode or namespace-mode). | ||
|
|
||
|
|
||
| * Deploying setup on new chaos infrastructures has ‘X’ and ‘Done’ buttons (CHAOS-1289) |
There was a problem hiding this comment.
Please check if X and Done buttons should be in bold.
|
|
||
|
|
||
| * Limit of 1,000 experiments still allows scheduling chaos experiments and connecting to new (or existing) infrastructure (CHAOS-1261) | ||
| * This release displays a message stating that the resource limits have been reached once you exceed the 1,000 experiment creation limit. You will be able to schedule chaos experiments and connect to chaos infrastructures (new and existing ones) even after you hit the limit of 1000 experiments in chaos. |
There was a problem hiding this comment.
Starting this release, a message is displayed..
release-notes/chaos-engineering.md
Outdated
| * This release downloads the upgraded manifest file with the yml extension when you click **re-download the manifest**. | ||
|
|
||
|
|
||
| * Limit of 1,000 experiments still allows scheduling chaos experiments and connecting to new (or existing) infrastructure (CHAOS-1261) |
There was a problem hiding this comment.
Does this mean that I can schedule experiments even if I cross the 1000 limit? If yes, please see if you can rephrase this.
|
|
||
|
|
||
| * Reduced response time of the communication chaos module and other Harness services (CHAOS-1262) | ||
| * This release reduces the response time when the chaos module communicates with other Harness services. This is because the chaos module doesn’t use intermediate gateways for communication, but rather hits the Harness service directly. |
There was a problem hiding this comment.
Starting this release, the response time when the chaos module communicates with other Harness services is reduced.
|
|
||
|
|
||
| * **All runs** screen changed to **Run history** (CHAOS-995) | ||
| * This release has changed the **All runs** screen name to **Run history**. The **Run history** screen displays all the runs of a chaos experiment. Clicking on a specific run of the chaos experiment displays the fault executed, the status of the experiment, the status of the probes, the fault weights, and the duration of the experiment. |
There was a problem hiding this comment.
Starting this release, the All runs screen name is changed to Run history.
| @@ -43,7 +107,7 @@ From this release onward, chaos infrastructures will communicate with the contro | |||
| * This release adds search functionality when selecting an experiment template from chaos hub. You can also filter the experiments you want to view or select from the chaos hub. This allows you to select and run your experiment without searching multiple experiments. | |||
|
|
|||
| * Chaos infrastructure manifest file extension changed to .yaml (CHAOS-1037) | |||
| * This release changes the downloadable chaos infrastructure manifest file extension from .yml to .yaml. | |||
| * This release changes the downloadable chaos infrastructure manifest file extension from yml to yaml. | |||
There was a problem hiding this comment.
Starting this release, the downloadable chaos infrastructure manifest file extension is changed from yml to yaml.
release-notes/chaos-engineering.md
Outdated
| * This release adds a new access control, **Execute**, in addition to **View**, **Create/Edit**, and **Delete**. **Execute** allows you to execute the chaos experiments, whereas **Create/Edit** will only allow you to create a chaos experiment or edit an existing chaos experiment. The newly added access control provides granularity while working with chaos experiments. | ||
|
|
||
|
|
||
| * Update button to see available updates for a chaos experiment (CHAOS-1069) |
There was a problem hiding this comment.
| * Update button to see available updates for a chaos experiment (CHAOS-1069) | |
| * Update button to see available updates for a chaos infrastructure (CHAOS-1069) |
release-notes/chaos-engineering.md
Outdated
|
|
||
|
|
||
| * Update button to see available updates for a chaos experiment (CHAOS-1069) | ||
| * This release displays an ‘Update’ button alongside the chaos experiment. When you click this button, it shows if an update is available for the experiment. |
There was a problem hiding this comment.
| * This release displays an ‘Update’ button alongside the chaos experiment. When you click this button, it shows if an update is available for the experiment. | |
| * This release displays an ‘Update’ button alongside the chaos infrastructure. When you click this button, it shows if an update is available for the infrastructure. |
release-notes/chaos-engineering.md
Outdated
|
|
||
| * When tuning the target application, the OpenShift cluster timed out before fetching the information from your cluster. This issue is fixed. The duration of timeout has been increased. (CHAOS-1299) | ||
|
|
||
| * When the labels of a chaos experiment, such as ‘Run by’ included special characters, the workflow would not run because Kubernetes doesn’t allow special characters in the workflow. This issue is fixed. The labels (which are a part of the manifest file) are encoded before sending the workflow to the cluster and decoded while presenting on the user interface. (CHAOS-1281) |
There was a problem hiding this comment.
| * When the labels of a chaos experiment, such as ‘Run by’ included special characters, the workflow would not run because Kubernetes doesn’t allow special characters in the workflow. This issue is fixed. The labels (which are a part of the manifest file) are encoded before sending the workflow to the cluster and decoded while presenting on the user interface. (CHAOS-1281) | |
| * When the labels of a chaos experiment, such as ‘Run by’ included special characters, the experiment would not run because Kubernetes doesn’t allow special characters in the labels. This issue is fixed. The labels (which are a part of the manifest file) are encoded before sending the experiment to the cluster and decoded while presenting on the user interface. (CHAOS-1281) |
Address review comments (peer and technical) Signed-off-by: Smriti S <smriti.satyanarayana@harness.io>
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
Update date Update version Signed-off-by: Smriti S <smriti.satyanarayana@harness.io>
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app |
Path: "Documentation/Chaos engineering/release-notes/chaos-engineering"
URL: https://hdh.pr.harness.io/pr-1113/release-notes/chaos-engineering
Signed-off-by: Smriti S smriti.satyanarayana@harness.io