Skip to content

2.12.0
Compare
Choose a tag to compare
@Jonsy13 Jonsy13 released this 12 Aug 16:45
2.12.0
90021fe
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Release Notes (2.12.0)

Core Component Updates:

  • Adds toxicity support in HTTP Chaos experiments. Toxicity can be used to define the percentage of HTTP requests that should be affected for example 50% toxicity will mean only half of the HTTP requests will be affected. litmuschaos/litmus-go#544

  • Introduce randomized status code selection when multiple status code is provided as a fault in input for HTTP status code chaos experiment. litmuschaos/litmus-go#545

  • Adds support for experiments with helper pod in chaoslib in litmus SDK with this, the user can create a chaos template with helper pod model using the same litmus SDK. litmuschaos/litmus-go#546

  • Adds support for imagePullSecret in source cmd Probe this will enable the user run cmd probe pod with private image. litmuschaos/chaos-operator#415

  • Fixes litmus-e2e pipeline and unit test pipeline by specifying version for creating k3s cluster. litmuschaos/litmus-e2e#391

  • Fixes chaos execution on openshift-4.x by providing finalizer permission to chaos-operator service account, with the new operator upgrade in litmus 2.11.0 brings down this requirement. litmuschaos/chaos-operator#413

  • Fixes chaos-operator vulnerabilities detected by snyc and trivy in the build pipeline. litmuschaos/chaos-operator#414

ChaosCenter Updates -

  • Adds an advanced tuning feature for experiments individually with more supported configurations #3715

  • Adds a new feature for connecting a remote ChaosHub to ChaosCenter #3722

  • Adds a new API getServerVersion for fetching GQL server version #3721

  • Makes clusterIP to be used by default for generating endpoints for internal delegates/self-agent #3709

  • Adds an additional permission required for execution plane to be deployed in openshift clusters #3708

  • Upgrades gopkgs for Chaos-Operator to v2.11.0 & Argo to v3.3.1 reducing some of the vulnerabilities in Graphql-server & Subscriber. #3718

  • Removes the support for dashboards & datasources configuration from UI. #3716

  • Fixes a bug of workflow getting failed when using dex/ providing email as username #3705

  • Fixes a bug of frontend crashing when providing invalid cron-syntax #3714

  • Fixes a bug when editing schedule for first time due to state not getting cleaned up #3727

  • Adds fix for workflows comparison plot not coming #3729

  • Adds fix for logs not coming for install experiments step #3729

  • Adds fix for UI not getting updated for deactivate user and created_at column showing invalid date in Users Table in admin-account #3733

Litmusctl Updates -

  • With litmusctl 0.12.0 release, we have updated some commands with the new terminologies ✨:

    • litmusctl connect agent is now litmusctl connect chaos-delegate
    • litmusctl disconnect agent is now litmusctl disconnect chaos-delegate
    • litmusctl get agents is now litmusctl get chaos-delegates
    • litmusctl create workflow is now litmusctl create chaos-scenario
    • litmusctl delete workflow is now litmusctl delete chaos-scenario
    • litmusctl describe workflow is now litmusctl describe chaos-scenario
    • litmusctl get workflows is now litmusctl get chaos-scenarios
    • litmusctl get workflowruns is now litmusctl get chaos-scenario-runs
    • litmusctl upgrade agent is now litmusctl upgrade chaos-delegate

  • Improves error handling logic for upgrade chaos-delegate, describe chaos-scenario and disconnect agent commands. litmuschaos/litmusctl#81

  • Adds --kubeconfig flag in upgrade chaos-delegate command. litmuschaos/litmusctl#89

  • Adds fix for passing namespace in the SelfSubjectAccessReviews function. litmuschaos/litmusctl#82

  • litmusctl will now prompt if installed version of litmusctl is not compatible with installed litmus control plane. litmuschaos/litmusctl#84

  • Users can check the compatibility matrix in the readme or by using litmusctl version command. litmuschaos/litmusctl#84

Users can also find the commands in readme: https://github.com/litmuschaos/litmusctl#readme

NOTE: - Along with above terminologies updates, we will also be updating directory structure of ChaosHub for better readability and scalability of experiments and scenarios. With upcoming release, the charts directory will be renamed to experiments directory and workflows will be renamed to scenarios directory. Same changes have been already done in 2.11.0 branch/version of ChaosHub. So, Users are requested to upgrade their ChaosHub directory structure with provided changes before upgrading to upcoming release - 2.13.0 version of ChaosCenter.

Shoutouts!

Thanks to our existing and new contributors for this release- @dnielsen @deividMatos @amityt @Saranya-jena @SarthakJain26 @Adarshkumar14 @imrajdas @Jonsy13

Full Changelog: 2.11.0...2.12.0

Installation

Litmus-2.12.0 (Stable) cluster scope manifest

kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.12.0/mkdocs/docs/2.12.0/litmus-2.12.0.yaml

Or

Litmus-2.12.0 (Stable) namespace scope manifest.

#Create a namespace eg: litmus
kubectl create ns litmus
#Install CRDs, if SELF_AGENT env is set to TRUE
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.12.0/litmus-portal-crds-2.12.0.yml
#Install ChaosCenter
kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/2.12.0/litmus-namespaced-2.12.0.yaml -n litmus

Upgrading from 2.11.0 to 2.12.0

kubectl apply -f https://raw.githubusercontent.com/litmuschaos/litmus/2.12.0/mkdocs/docs/2.12.0/upgrade-agent.yaml

Contributors

dnielsen, imrajdas, and 6 other contributors
Assets 2
Loading
0 Join discussion