forked from litmuschaos/litmus
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstrings.en.yaml
1207 lines (1207 loc) · 47 KB
/
strings.en.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
404Error: Oops, we could not find this page.
Executor: Executor
FRI: FRI
MON: MON
NASlash: N/A
SAT: SAT
SUN: SUN
THU: THU
TUE: TUE
WED: WED
aboutChaosCTL: >-
You can configure and tune your chaos infrastructure, and download the
deployment manifest . This manifest is applied to your Kubernetes cluster.
Below mentioned Kubernetes permissions are required to install chaos
infrastructure:
acceptInvitation: Accept Invitation
accessToAllNamespaces: Access to all namespaces
accessToken: Access Token
accessTokenPlaceholder: Enter your Personal Access Token
accessType: Access Type
account: Account
accountURL: Account URL
actionItems: Action Items
active: Active
activeMembers: Active members
actualResilienceScore: Actual Resilience Score
add: Add
addExperimentToChaosHub: Add Experiment to ChaosHub
addNewCluster: Add new cluster (Coming soon!)
addNewCustomizedProbes: Add new customized probes to the fault
addNewProbes: Select or Add new probes
addNodeSelectorAgentDeployment: Add NodeSelector in Chaos Infrastructure deployment
addOrClick: Add a probe, or click on a probe to view its details
addProbe: Add Probe
addResilienceStep: Add Resilience Step
addRow: Add Row
addSystemProbe: Add a System Probe
addToChaosHub: Add to ChaosHub
addToFault: Add to Fault
addToTemplate: Add to Template
addTolerationAgentDeployment: Add Toleration in Chaos Infrastructure deployment
addViewSummaryNotes: Add/View Summary Notes
addtoHubLoading: Adding to ChaosHub, please wait...
advanced: Advanced (Optional)
advancedOptions: Advanced Options
all: All
allChaosEnabled: All Chaos Enabled Infrastructures
allExecutions: All Executions
allFaultsExecuted: All your faults executed without any issue
allRuns: All Runs
alreadyExists: '{{value}} already exists'
alreadyExistsID: Entered id '{{value}}' already exists
apiTokens: API Tokens
appKind: App Kind
appKindName: app_kind
appLabel: App Label
appLabelName: app_label
appNameSpace: App Namespace
apply: Apply
applyChanges: Apply Changes
at: At
atAGlance: At a Glance
attempt: Attempt
authentication: Authentication
authenticationType: Authentication Type
averageResilienceScore: Average Resilience Score
back: Back
basic: Basic
basicInformation: Basic Information
blankCanvasDescription: >-
Chaos Experiment is a set of different operations coupled together to achieve
desired chaos impact on a Kubernetes Cluster. It is useful in automating a
series of pre-conditioning steps or action which is necessary to be performed
before triggering the chaos injection. A Chaos Experiment can also be used to
perform different operations paralleled to achieve a desired chaos injection
experiment.
blankCanvasTitle: Select and arrange faults from ChaosHubs to create your desire sequence.
blobLogsNotAvailable: Logs are not available for this node.
branch: Branch
cancel: Cancel
cannotPushToDefault: Cannot push experiment to default ChaosHub
cannotReRun: Cannot re-run an already running experiment
changePassword: Change Password
chaos: Chaos
chaosComponentInstallation: Chaos Components Installation
chaosController: Chaos Controller
chaosEnableFailed: Failed to register the chaos enablement job, please contact support
chaosEngineName: ChaosEngine Name
chaosEngineResult: Chaos Engine Result
chaosExperiment: Chaos Experiment
chaosExperiments: Chaos Experiments
chaosFaults: Chaos Faults
chaosHub: ChaosHub
chaosHubExperiment: ChaosHub Experiment
chaosHubFault: ChaosHub Fault
chaosHubNoExp: No experiments found in this ChaosHub
chaosHubNoFault: No faults found in this ChaosHub
chaosHubNoSearchExperiment: No experiments found matching term '{{searchTerm}}'
chaosHubNoSearchFault: No faults found matching term '{{searchTerm}}'
chaosHubReferenceFielPlaceholder: '- Select a ChaosHub -'
chaosHubStep1: Step 1 -> Click on "Launch Experiment".
chaosHubStep2: Step 2 -> Choose a target Chaos Infrastructure.
chaosHubStep3: Step 3 -> Configure the experiment and run as per your needs.
chaosIncidentsDetected: Chaos incidents detected
chaosIncidentsDiscovered: Chaos Incidents discovered?
chaosInfraVersionAvailable: Chaos Infrastructure version {{version}} is available
chaosInfrastructureDesc: >-
Kubernetes Chaos Infrastructures are the target deployments that are synced
with your source manifests.
chaosInfrastructureDescription: Add a description for your Chaos Infrastructure
chaosInfrastructureDetails: Chaos Infrastructure Details
chaosInfrastructureLogs: Chaos Infrastructure Logs (Coming Soon!)
chaosInfrastructureNamespace: Installation Location (Namespace)
chaosInfrastructureOverview: Chaos Infrastructure Overview
chaosInfrastructureSuccess: Chaos Infrastructure successfully created
chaosInfrastructureText: Chaos Infrastructure
chaosInfrastructures: Chaos Infrastructures
chaosResultNotAvailable: Chaos Result not available yet
chaosResults: Chaos Results
chaosStudio: Chaos Studio
chaoshubDisconnectedWillSync: ChaosHub is disconnected, will attempt to sync
chaoshubs: ChaosHubs
checkConnection: Check Connection
checkLogs: Check the Chaos Infrastructure Logs
checkStatus: Check the status of your Chaos Infrastructure on your cluster
chooseAccessType: Choose Access Type
chooseAuthenticationType: Choose Authentication Type
chooseHubAccess: Choose Hub Access
chooseMembersAddTheProject: Choose members to add to the project
chooseProbeMode: Choose Mode for probe to be executed
clearSearch: Clear search
clickDownload: >-
Click on the “Download” button below to download the YML file to a machine
where you have kubectl installed and have access to your Kubernetes cluster.
clone: Clone
cloneExperiment: Clone Experiment
closeTuneConfirmation: Close tune fault configuration?
closeTuneConfirmationDescription: >-
Changes to your tune fault configuration will be lost if you do not apply your
changes.
clusterScopeDescription: >-
Allows LitmusChaos to perform and monitor chaos in all namespaces in the
cluster.
clusterWide: Cluster-wide
clusterWideAccess: Cluster-wide access
cmdDescription: >-
Allows developers to run shell commands and match the resulting output as part
of the entry/exit criteria.
cmdProbeDetails: >-
The command probe allows developers to run shell commands and match the
resulting output as part of the entry/exit criteria. The intent behind this
probe was to allow users to implement a non-standard & imperative way of
expressing their hypothesis. For example, the cmdProbe enables you to check
for specific data within a database, parse the value out of a JSON blob being
dumped into a certain path, or check for the existence of a particular string
in the service logs.
cmdProbeTitle: Execute any user-desired health-check function implemented as a shell command
collaborators: Collaborators
comingSoon: Coming Soon
command: Command
comparator: Comparator
comparisonCriteria: Comparison Criteria
completed: Completed
configure: Configure
configureChaosInfrastructure: Configure Chaos Infrastructure
configureDetails: Configure Details
configureProperties: Configure Properties
confirm: Confirm
confirmPassword: Confirm Password
confirmText: Are you sure you want to proceed?
connectChaosHub: Connect ChaosHub
connectHub: Connect Hub
connectInfraKubernetes: >-
Open your target cluster and run the following command to connect to your
kubernetes infrastructure
connectInfraTooltip: >-
Note - It seems the cluster you have selected already has a cluster scope
chaos access on it, either remove it or continue with namespace mode.
connected: Connected
connectingChaosHub: Connecting ChaosHub
connectionModal:
method: Select method of connection
options:
option1:
icon: github
text: Connect a new git repo
option2:
icon: argo
text: Connect other repo
connectionStatus: Connection Status
consoleLogs: Console Logs
continue: Continue
copiedToClipboard: Copied to clipboard
copyPrompt: >-
Copy the downloaded YML to a machine where you have kubectl installed and have
access to your Kubernetes cluster.
copyPrompt1: 2. Apply the Chaos CRDs manually
copyPrompt2: >-
3. Copy the downloaded YML to a machine where you have kubectl installed and
have access to your Kubernetes cluster.
crdCopyPrompt: Apply the Chaos CRDs manually
createChaosExperiment: Create Chaos Experiment
createNamespace: 1. Create the namespace on your Kubernetes cluster
createNewToken: Create New Token
createNewUser: Create New User
createProject: Create Project
createRecurringSchedule: Create recurring schedule
created: Created
createdAt: Created At
createdBy: Created By
createdByUser: Created By User
createdOn: Created On
creationTime: Creation Time
criteria: Criteria
criteriaForData: Criteria for data
cron: Cron
cronDisabled: Cron Schedule is disabled
cronExpression: Cron Expression
cronExpressionRequired: Cron Expression required
cronHalted: This cron experiment as been halted successfully.
cronResumed: This cron experiment has re-scheduled successfully.
cronSelectOption: Cron (Recurring run)
cronText: >-
The experiment will run periodically according to the cron provided below. You
can stop the schedule anytime you want.
currentRun: Current Run
currentUTCTime: Current UTC Time
customImageRegistry: Custom Image Registry
customLabel: Custom
customRepo: Custom Repo
customValueText: All YAML files will use the custom values.
customValues: Use Custom Values
daily: Daily
dailyMessage: Your chaos experiment will run daily at your chosen time.
dateExecuted: Date Executed
dayOfMonthLabel: Day of month
dayOfWeekLabel: Day of week
days: '{{count}} days'
declineInvitation: Decline Invitation
declineInvitationDescription: Are you sure you want to decline the invitation?
defaultValueOption: Use Default Values
defaultValueText: >-
All YAML files use these default values provided by Litmus. These values
cannot be changed.
degelateNotActive: Selected infrastructure is inactive. Please select an active one.
delete: Delete
deleteApiTokenDescription: Are you sure you want to delete this API Token?
deleteChaosInfrastructure: Are you sure you want to disable this Chaos Infrastructure?
deleteExperiment: Delete Experiment
deleteExperimentDesc: >-
Deletes all the experiment runs from the chaos control plane. This will also
stop all experiments runs that are running.
deleteExperimentHeading: Delete this experiment?
deleteProbe: Delete Probe
deleteProbeDesc: >-
Deletes the probe and all the associations with experiment runs from the chaos
control plane. This will also misplace any analytics that had incurred for the
previous runs for this probe.
deleteProbeHeading: Delete this probe?
deleteProject: Delete Project
deleteProjectWarning: Do you want to delete selected project?
deleteSuccess: Chaos Infrastructure Successfully Disabled
deployChaosInfrastructure: Deploying your Infrastructure
deployProbe: Deploy new Probe
deploySetup: Deploy the setup
deployedOn: Deployed using
description: Description
descriptionOptional: Description (Optional)
details: Details
detailsAndProperties: Details & Properties
disable: Disable
disableChaosInfrastructure: Disable Chaos Infrastructure
disableCron: Disable Cron
disableCronDesc: This will disable the cron schedule for this experiment.
disableUser: Disable User
disableUserDescription: Are you sure you want to disable this user?
discard: Discard
discardExperiment: Are you sure you want to discard the current experiment?
discardProbeConfiguration: Discard all probe configurations which are currently entered?
disconnectDescriptionClusterMode: Disable Chaos for this cluster.
disconnectDescriptionNamespaceMode: Disable Chaos for this namespace.
disconnected: Disconnected
docker: docker.io
done: Done
download: Download
downloadChaosInfrastructureManifest: Re-Download the manifest
downloadExperiment: Download Manifest
downloadSuccess: Download request successfully sent
downloadYAML: Download YML
downloadYAMLFile: Step 1 - Download YML file
downloadedSuccessfully: Downloaded successfully
duration: Duration
edit: Edit
editChaosHub: Edit ChaosHub
editEnvironment: Edit Environment
editExperiment: Edit Experiment
editExperimentCopy: Edit Copy
editExperimentOptions: Do you want to edit the same experiment or edit a copy?
editExperimentSame: Edit Same
editHubDescription: >-
We recommend you to create a new Experiment in case of addition/deletion of
faults or probes, as editing experiments with new faults or probes,
co-relation of analytics might get impacted.
editInChaosStudio: Edit in Chaos Studio
editName: Edit Name
editProbe: Edit Probe
editProjectName: Edit Project Name
editSameExperimentDescription: >-
When you edit directly on the existing experiment, you will not be able to
change the name and target environment/infrastructures of this experiment. And
your current experiment with run history will be overwritten.
editSameExperimentTitle: Edit on the existing Experiment
editYaml: Edit Yaml
editingChaosHub: Editing ChaosHub
effect: Effect
email: Email
emailIsRequired: Email is a required field
enableChaosInfraButton: Enable Chaos in Environments
enableChaosInfrastructure: Enable chaos infrastructure to run your first chaos experiment
enableChaosInfrastructureDesc: >-
In order to run Chaos Experiments, you need to enable chaos infrastructure in
the Environments
enableCron: Enable Cron
enableCronDesc: This will enable the cron schedule for this experiment.
enableImageRegistryChanges: Enable Image Registry Changes
enableSSLCheck: Enable SSL/TLS check
enableUser: Enable User
enableUserDescription: Are you sure you want to enable this user?
enablingChaos: Enabling chaos...
endTime: End Time
endedAt: Ended at
endpoint: Endpoint
enterCustomCron: Enter a custom cron expression
enterHubAccountURL: Enter Hub Account URL
enterHubName: Enter Hub Name
enterHubRepositoryBranch: Enter Hub Repository Branch
enterHubRepositoryName: Enter Hub Repository Name
enterHubRepositoryURL: Enter Hub Repository URL
enterNewPassword: Enter new password
enterOldPassword: Enter old password
enterProjectName: Enter Project Name
enterYourEmail: Enter your email
enterYourName: Enter your name
enterYourPassword: Enter your password
enterYourUsername: Enter your username
environment: Environment
environmentDescription: >-
An environment is the place where you will deploy your cluster for chaos
testing
environmentError: It seems there was an error fetching the Environment Details.
environmentNameIsRequired: Environment Name is a required field
environmentType: Environment Type
environments: Environments
error: Error
errorApplyChanges: Error in Applying the Changes. Please enter correct input values.
errorFetchName: Error in fetching the name.
errorInYamlDescription: There are some errors in the file, please check YAML file for errors.
evaluationTimeout: Evaluation timeout
executedBy: Executed by
executedOn: Executed on
executionDetails: Execution details goes here
executionError: Execution Error
expand: expand
executionHistory: Execution History
executionID: Execution ID
executionOverview: Execution Overview
executionStatus: Execution Status
exhausted: Exhausted
expCategory: Experiment Category Tag
expDesc: Experiment Description
expName: Experiment Name
expSaved: Experiment saved successfully
expectedResilienceScore: Expected Resilience Score
expectedResponseCode: Expected Response Code
experiment: Experiment
experimentActivity: Experiment Activity
experimentBuilder: Experiment Builder
experimentDeleted: The experiment has been deleted successfully.
experimentDeletedSuccessfully: Experiment deleted successfully
experimentID: Experiment ID
experimentInFault: Predefined Chaos Experiments using this Fault
experimentIsRunning: Experiment execution in progress. Please wait.
experimentNamespace: Experiment Namespace
experimentOverview: Experiment Overview
experimentPreview: Experiment Preview
experimentRunDetails: Experiment Run Details
experimentRunID: Experiment Run ID
experimentRuns: Experiment Runs
experimentStopSuccessMessage: Experiment successfully stopped
experimentType: Experiment Type
experiments: Experiments
expiresAt: Expires At
expiresIn: Expires In
expressionBreakdown: Expression Breakdown
failStep: Fail Step
failed: Failed
failedRuns: Failed Runs
fault: Fault
faultActivity: Fault Activity
faultConfiguration: Fault Configuration
faultDetails: Fault Details
faultShouldHaveAtleastOneProbe: Fault should have at least one probe available
faultSummary: Fault Summary
faultVerdict: Fault Verdict
faults: Faults
faultsContained: Faults Contained
faultsHaveProbeFailures: Faults have Probe Failures
faultsLibrary: Faults Library
featureRestriction:
experimentsPerMonthLevelUp: >-
You have used {{ count }} / {{ experimentsLimit }} free experiment runs this
month. Consider upgrading for more experiments runs.
initialDeploymentsWarningActive: >-
You have used {{ warningLimit }}% of experiment runs included in the free
plan. The free plan is restricted to 10 experiment runs per month.
resourceLevelUpFree: >-
You have used {{ resourceLimit }} {{ resourceName }} included in the free
plan. Consider upgrading to unlock more resources.
resourceLevelUpTeam: >-
You have used {{ resourceLimit }} resources included in the team plan.
Consider upgrading to unlock more resources.
resourceOveruseEnterprise: >-
You have exceeded your resource subscription limit. Consider increasing your
limits to keep shipping.
fieldMaxLength: Length should be {{length}} characters maximum.
fieldMinLength: Length should be {{length}} characters minimum.
fieldSelector: Field Selector
fixAllErrors: Fix all the errors indicated in the YAML Editor to resolve the issue.
generateSSH: Generate New SSH Key
genericResourceNotFoundError: >-
{{resource}} [{{resourceID}}] under Project [{{projectID}}] does not exist or
has been deleted.
gitConnection: Repository Connection
gitOps: GitOps
gitops: Gitops
goBack: Go back to previous page
goChaosHome: Go to Home
greatJob: Great Job
group: Group
healthy: Healthy
history: History
hostedOn: Hosted on
hostedOnAgent: Hosted on Chaos Infrastructure
hourly: Hourly
hourlyMessage: Your chaos experiment will run hourly at your chosen minute.
hoursAnd: hours(s) and
hoursLabel: Hours
hoverFaultToViewDetails: Hover over a fault to view details
howToFindServiceAccount: How to find Service Account Name?
howToUseExp: How to use the Experiment
httpDescription: >-
Allows developers to run HTTP commands and match the resulting output as part
of the entry/exit criteria.
httpProbeDetails: >-
The httpProbe allows developers to specify a URL which the experiment uses to
gauge health/service availability (or other custom conditions) as part of the
entry/exit criteria. The received status code is mapped against an expected
status. It supports http Get and Post methods.
httpProbeTitle: Query health/downstream URLs
hubAccess: Hub Access
hubConnectedSuccessfully: Hub Connected Successfully
hubDeletedSuccessfully: Hub Deleted Successfully
hubEditedSuccessfully: Hub Edited Successfully
hubName: Hub Name
hubRepositoryBranch: Hub Repository Branch
hubRepositoryURL: Repository URL
hypothesis: hypothesis
id: ID
idlowerCase: id
imageRegistry: Image Registry
imageRegistryUpdateSuccess: Image Registry added successfully
imageSecret: Image Secret
imageSecretPlaceholder: Enter your Image Secret
improveResilienceOfTheDeployedService: Improve resilience of the deployed service
inactive: Inactive
inactiveTooltip: >-
This infrastructure is Inactive as your deployment may have encountered a
problem. Please check the deployment logs
infraName: Infrastructure Name
infrastructure: Infrastructure
infrastructureCommand: >-
Run the following command to apply the Chaos infrastructure to your Kubernetes
Cluster
infrastructureRegistered: >-
Your infrastructure has been registered. The infrastructure takes up to 3-5
minutes to be available for chaos testing. You can check the status in
Environment -> Infrastructure list.
infrastructureStates: Learn more about the states of Infrastructure
infrastructureType: Infrastructure type
infrastructures: Infrastructures
initialDelay: Initial Delay
initialDelaySeconds: Initial Delay Seconds
insecureSkipVerify: Insecure skip verify
installYaml: Install Chaos Infrastructure using YML
interval: Interval
intervalOptional: Interval (Optional)
invalidEmailText: Please enter a valid email address
invalidSelection: Invalid Selection
invalidText: Invalid
invalidYaml: The Visual Editor is disabled because of the errors in the YAML file.
invitationRemoveSuccess: Invitation cancelled successfully
invitationSuccess: Invitation sent successfully
invitations: Invitations
inviteAs: Invite as
invitedBy: Invited By
invitedByOthers: Invited By Others
isRequired: '{{field}} is required field'
issueSupport: If the issue still persists, consider reaching out to support!
k8sDescription: >-
Addresses verification of the desired resource state by allowing users to
define the Kubernetes GVR (group-version-resource) with appropriate filters
(field selectors/label selectors)
k8sProbeDetails: >-
The k8sProbe addresses verification of the desired resource state by allowing
users to define the Kubernetes GVR (group-version-resource) with appropriate
filters (field selectors/label selectors). The experiment makes use of the
Kubernetes Dynamic Client to achieve this. It supports create, delete, present
and absent operations.
k8sProbeTitle: Perform CRUD operations against native & custom Kubernetes resources
key: Key
kubectl: Kubectl
kubernetes: Kubernetes
kubernetesChaosInfrastructureClusterScopeDeleteStepTwo: 2. Delete the remaining components
kubernetesChaosInfrastructureDeleteStepOne: 1. Delete the chaos experiment, engine, and result
kubernetesChaosInfrastructureNamespaceScopeDeleteStepFour: 4. Delete the namespace
kubernetesChaosInfrastructureNamespaceScopeDeleteStepThree: 3. Delete the remaining components
kubernetesChaosInfrastructureNamespaceScopeDeleteStepTwo: 2. Delete the CRDs
kubernetesClusterDetails: K8s Cluster Details
kubernetesInfrastructureDeleteCRDSNote: >-
Note: If you have another Kubernetes chaos infrastructure on this cluster
under a different namespace then skip the below step (2)
kubernetesInfrastructureDeleteNote: >-
Note: Please download the chaos infrastructure manifest from the menu and run
the following command on your Kubernetes cluster to clean up the
infrastructure resources
kubernetesPermissions:
nameSpace: To create namespace for the chaos infrastructure namespace.
statefulSets: To create deployments for the chaos infrastructure plane.
kubernetesPrerequisites: Kubernetes prerequisites
kubernetesSetupInstructions: Kubernetes Setup Instructions
labelSelector: Label Selector
lastHeartBeat: Last HeartBeat
lastModified: Last Modified
lastResilienceScore: Last Resilience Score
lastRun: Last Run
lastSyncedAt: Last Synced at
lastUpdatedBy: Last Updated By
latestRun: Latest Run
latestRunFallbackText: No Experiment Runs found
launchExperiment: Launch Experiment
learnMore: Learn More
leaveProject: Leave Project
leaveProjectDescription: Are you sure you want to leave the project?
leaveThisPage: Leave this Page
letsGetStarted: Let`s get started
litmus: Litmus
litmusChaos: LitmusChaos
litmuschaos: litmuschaos
loading: Loading, please wait...
local: Locally in Litmus
logErrorMessage: Unable to fetch logs from log service, please try after some time.
loginDescription: Login to create, orchestrate, analyze and collaborate your Chaos Experiments.
loginToContinue: login to continue
logs: Logs
logsOptional: Logs (Optional)
mainTitle: How do you want to start off?
manifestDownloadUnsuccessful: Manifest download is unavailable!
manifestMissing: Manifest is missing! Please check your ChaosHub.
manual: Manual
manualInterruption: Manual Interruption needed
manually: '| Manually'
markRunAsComplete: Mark Run as Complete
markRunAsCompleteDescription: This will mark the run as complete and you will no longer be able to re-run.
meetsExpectations: The resilience score has met the expectation.
members: Members
membersNotAvailableMessage: No active project members available
membersNotAvailableTitle: No members present
menuItems:
deleteHub: Delete Hub
editHub: Edit Hub
syncHub: Sync Hub
viewHub: View Hub
method: Method
minute: Minute
minutesAfterTheHour: minute(s) after the hour
minutesLabel: Minutes
minutesParentheses: minute(s)
mode: Mode
moduleName: Chaos Module
monitorCluster: >-
Allows LitmusChaos to perform and monitor chaos in all namespaces available in
this cluster
monitorNamespace: >-
Allows LitmusChaos to perform and monitor chaos in a particular namespace
available in this cluster
monthLabel: Month
monthly: Monthly
monthlyMessage: Your chaos experiment will run monthly at your chosen day and time.
monthsParentheses: month(s)
mostRecentDirection: Latest one on right side
mustBeInteger: '{{field}} must be an integer'
mustBePositive: '{{field}} must be a positive number'
myProfile: My Profile
na: Not Available
name: Name
nameIdDescriptionTags:
descriptionPlaceholder: Enter Description
namePlaceholder: Enter Name
optionalField: '{{name}} (optional)'
tagsLabel: Tags
nameIsARequiredField: Name is a required field
nameIsRequired: Name is a required in order to update.
nameValidText: Name can only contain alphabets.
namespace: Namespace
namespaceScopeDescription: Allows LitmusChaos to perform and monitor chaos in a namespace.
namespaceWide: Namespace-wide
navigationCheckText: >-
You have unsaved changes. Are you sure you want to leave this page without
saving?
navigationCheckTitle: Close without saving?
needAttention: Needs Attention
newChaosExperiment: New Chaos Experiment
newChaosHub: New ChaosHub
newChaosInfrastructure: Enable Chaos
newEnvironment: New Environment
newExperiment: New Experiment
newMember: New Member
newPassword: New Password
newProbe: New Probe
newToken: New Token
newUpdates: New Updates
newUser: New User
newUserNoExperiments:
subtitle: >-
A chaos experiment contains a series of chaos faults and chaos probes to
verify the resilience of your service
title: There are no Chaos Experiments in your project
newUserNoInfra:
title: There are no active Chaos Infrastructures in your project
next: Next
nextRun: Next Run
nextSelectChaosExperiments: Next -> Select Chaos Experiments
noAnalysis: No Analysis
noApiTokensFound: No API Tokens found
noChaosHubSelected: No ChaosHubs selected
noChaosInfrastructure: There are no Kubernetes Chaos Infrastructures in this Environment
noChaosInfrastructureFound: No Kuberenetes chaos infrastructure found!
noClustersFound: Sorry, we can’t find any available clusters
noData:
message: Oops, something went wrong on our end. Please contact Admin.
title: No Data Found
noDataCV: No Data
noDataToDisplay: No data to display
noDescriptionProvided: No description provided
noEnvironmentFound: No Environments found
noEnvironmentFoundMessage: >-
No Environments found in this project, click on 'New Environment' to add
environments.
noExpFound: No Predefined Chaos Experiments found using this Fault.
noExperimentFoundMatchingSearch: No experiment found matching your search
noExperimentSelected: No experiment selected
noExperiments: No Experiments found
noExperimentsAdded: No experiments added
noExpiration: No Expiration
noFaults: No Faults found in selected hub
noFilteredActiveInfra: No active Chaos Infrastructures found for the search term
noFilteredData:
subtitle: Please try to modify your search criteria.
title: No records were found to match your search
noHealthyState: If the Chaos Infrastructure didn’t reach a healthy state
noInvitationsFound: No invitations found
noKubernetesChaosInfrastructureFound: >-
No Kubernetes Chaos infrastructure found matching "{{value}}". Please adjust
the search criteria and try again.
noLogs: Sorry, Logs are currently not available
noMonitoredService: No monitoring services found for
noProbeDescription: >-
Probes are lightweight, self-contained scripts that can be run against
Kubernetes applications to gather information about their behavior under
stress and failure conditions.
noProbeExecution: No Probe executions found
noProbeExecutionDetails:
subtitle: >-
Probes are pluggable checks that can be defined within the ChaosEngine for
any Chaos Fault
title: There are no executions for the selected probe in your project
noProbes: No probes configured
noProbesAvailable: No Probes available for this node
noProbesFound:
errorMessage: Error in fetching probes
message: Experiment has no probes yet, chaos step may still be executing.
title: No Probes found
noProject:
subtitle: >-
Create a project to to run chaos experiments on your applications and verify
resilience.
title: Get Started with Chaos Engineering
noProjectFoundMatchingSearch: No project found matching your search {{searchTerm}}
noProjectsFound: No projects found
noProjectsJoined: No projects joined
noResultsFound: No results found
noRunsFound: No runs found
noRunsFoundForThisExperiment: No runs found for this experiment
noTunables: >-
Unable to identify fault configurations correctly, please refer to the fault
troubleshoot docs to learn more.
noUserAddUsers: No users found, click on 'New User' to add users.
noWorkflowRun: No experiment runs found
nodeSelector: Node Selector
nodeSelectorPlaceholderForKey: Enter the key
nodeSelectorPlaceholderForValue: Enter the value
nodeSelectorText: >-
Node Selector is a selector which will result in all pods of the experiment to
be scheduled on the selected node.
nonCron: Non-Cron
nonCronSelectOption: Non-Cron (Single run)
nonCronText: >-
The experiment will run once after you click on Run. If you want to run it
again, you can trigger it manually.
nonProd: Non Prod
notMeetsExpectations: The resilience score didn't meet the expectation.
notMeetsExpectationsInterventionNeeded: >-
The resilience score did not meet the expectation. It needs the manual
intervention.
notStarted: NOT STARTED
notes: Notes
numberOfExperiments: Number of Experiments
objective: Objective
objectives: Objectives
observe: Observe
ofEvery: of every
oldPassword: Old Password
'on': 'On'
onThe: on the
onThisPage: ON THIS PAGE
openInNewTab: Open in new tab
operation: Operation
operator: Operator
optional: (Optional)
or: or
orderBy: Order By
organization: Organization
outOf: OUT OF
outOfSmall: out of
overallNodeResult: Overall Node Result
overallResiliencyScore: Overall Resilience Score
overview: Overview
overwriteYaml: Uploading a yaml will overwrite the existing one.
owner: Owner
parallel: Parallel
passed: Passed
passedRuns: Passed Runs
password: Password
passwordIsRequired: Password is a required field
passwordResetSuccess: Password reset successfully
passwordValidation: >-
Password must contain at least one uppercase letter, one lowercase letter, one
number and one special character
passwordsDoNotMatch: Passwords do not match
pauseRun: Pause Run
pending: Pending
pendingInvitationsNotAvailableMessage: No pending invitations present
pendingInvitationsNotAvailableTitle: No invitations present
pendingMembers: Pending members
pendingTime: >-
It may take 3-5 minutes after applying the manifest for the infrastructure to
be connected.
phase: Phase
platform: Platform
pleaseComplete: Please complete all the steps
pleaseSelectLeastOneExperiment: Please select at least one experiment
pleaseSpecifyYAMLValues: Please specify the values in the YAML script
points: point(s)
pollingInterval: Polling Interval
preProd: Pre-Prod
predefinedExperimentsNotFound: No Predefined Experiments found in this hub
preview: Preview
previous: Previous
private: Private
probeAddedSuccessfully: Probe added successfully, please apply changes before closing
probeConfiguration: Probe Configuration
probeDeletedSuccessfully: Probe Deleted Successfully
probeDetails: Probe Details
probeExecutionPreview: PROBE EXECUTION PREVIEW
probeInFault: Probe in fault
probeMetadataExists: >-
Probe metadata already exists in the experiment manifest, recommended to use
probe annotations instead otherwise you won't get any analytics
probeMode: Probe Mode
probeModeAlreadyExists: is already present with the same mode
probeModes:
Continuous: Continuous
ContinuousDesc: >-
The probe is executed continuously, with a specified polling interval during
the chaos injection.
EOT: EOT
EOTDesc: >-
The probe will check hypothesis at the End of the Test as a as a post-chaos
check.
EOTVerbose: End of Test (EOT)
Edge: Edge
EdgeDesc: The probe will check hypothesis both before and after the Test.
OnChaos: OnChaos
OnChaosDesc: >-
The probe is executed continuously, with a specified polling interval
strictly for chaos duration of chaos
SOT: SOT
SOTDesc: >-
The probe will check hypothesis at the Start of the Test as a as a pre-chaos
check.
SOTVerbose: Start of Test (SOT)
probeName: Probe Name
probeNotAttachedToRef: >-
is not attached to a proper reference, please add it to annotations as
probeRef
probeOverview: Probe Overview
probePassedSuccessfully: Probe passed successfully
probeProperties: Probe Properties
probeResult: Probe Result
probeResultNotAvailable: Probe result is not available.
probeResultsInPastRuns: Probe results in the past 10 runs
probeStatus: Probe Status
probeSuccessPercentage: Probe Success Percentage
probeSummary: Probe Summary
probeType: Probe Type
probeTypes:
cmdProbe: Command Probe
httpProbe: HTTP Probe
k8sProbe: K8S Probe
promProbe: Prometheus Probe
probeValidation:
accountIdentifier: Account identifier is a required field
apiTokenSecret: API Token Secret is a required field
apiTokenSecretName: API Token Secret Name is a required field
command: Probe command is a required field
criteria: Comparator criteria is a required field
endpoint: Probe endpoint is a required field
getCriteria: GET Criteria is a required field
getResponseCode: GET Response Code is a required field
interval: Probe interval is a required field
method: Probe method is a required field
name: Probe Name is a required field
operation: Probe operation is a required field
orgIdentifier: Organization identifier is a required field
platformEndpoint: Platform endpoint is a required field
postCriteria: POST Criteria is a required field
postResponseCode: POST Response Code is a required field
projectIdentifier: Project identifier is a required field
resource: Probe resource is a required field
timeFrame: Time Frame is a required field
timeout: Probe timeout is a required field
type: Comparator type is a required field
url: URL is a required field
value: Comparator value is a required field
version: Probe version is a required field
probes: Probes
probesArePassed: probes are passed
prod: Prod
project: Project
projectCreatedByYou: Your Projects
projectDashboard:
noProjectDescription: There are no projects.
noProjectText: No Projects
projectDeletedSuccess: Project Deleted Successfully
projectDescription: Project Description
projectFilters: Project Filters
projectNameIsRequired: Project name is a required in order to update.
projectNameValidText: Project name should be alphanumeric and can contain hyphen and spaces.
projectSetup: Project Setup
projects: Projects
projectsByInvite: Projects By Invite
projectsInTotal: project(s) in total
projectsJoined: Projects Joined
promDescription: >-
Allows users to define metrics-based SLOs in a declarative way and determine
the experiment verdict based on its success.
promProbeDetails: >-
The promProbe allows users to run Prometheus queries and match the resulting
output against specific conditions. The intent behind this probe is to allow
users to define metrics-based SLOs in a declarative way and determine the
experiment verdict based on its success. The probe runs the query on a
Prometheus server defined by the endpoint, and checks whether the output
satisfies the specified criteria. A PromQL query needs to be provided, whose
outcome is then used for the probe validation.
promProbeTitle: Execute promql queries and match prometheus metrics for specific criteria
properties: Properties
provideTargetApplicationDetails: Provide target application details where you want to induce the chaos
public: Public
query: Query
queryPath: Query path
ranAt: Ran at
range: range
rangeSliderInput: rangeSliderInput
rbacDescription: You are missing permission '{{permission}}' to perform this action.
rbacHeader: You do not have permission to perform this action
reEnterNewPassword: Re-enter new password
reEnterPassword: Re-enter password
reEnterYourPassword: Re-enter your password
reRunDesc: This will re-run the current experiment.
reRunExperiment: Run Experiment
reRunSuccessful: A new run scheduled successfully
readMore: ' Read more'
recentExecutionResults: Recent Execution Results
recentExecutions: Recent Executions
recentExperimentRuns: Recent Experiment Runs
recentlyUsed: Recently Used
recurringRun: Recurring Run (Cron)
recurringSchedule: Recurring Schedule
referencedBy: Referenced By
registry: Registry
registryName: Registry Name
registryType: Registry Type
remoteHub: Select Remote hub
remoteRepo: Remote Repository
remove: Remove
removeMember: Remove Member
removeMemberConfirmation: Are you sure you want to remove {{username}}?
removeProbeDesc: >-
This action will remove the probe from the manifest. Are you sure you want to
continue?
removeProbeHeading: Remove this probe?
repoBranchPlaceholder: Enter repository branch
repoURLPlaceholder: Enter repository URL
repository: Repository
required: Required
rerun: Rerun
resend: Resend
resetFilters: Reset Filters
resetPassword: Reset Password
resilienceOverview: Resilience Overview
resilienceProbes: Resilience Probes
resilienceRate: Resilience Rate
resilienceScoreOverview: Resilience Score Overview
resilienceScoreTooltip: >-
Latest application resilience measured based on this formula Σ(Weights(fault)
* Probe Percentage(fault)) / Σ Weights(fault).
resilienceScoreTrends: Resilience Score Trends
resilienceStepCanHelpYou: Resilience Step can help you
resilienceTabDescription: >-
Run controlled 'chaos' experiments to understand how real-world stress and
failures impact your systems. Create more reliable applications and
infrastructure.
resiliencyScore: Resilience Score
resource: Resource
resourceNames: Resource Names
responseCode: Response Code
responseTimeout: Response Timeout
responseType: Response Type
resultAfterExecution: Probe result would be available after execution completion
resultMetExpectations: Result met expectations
resultSummary: Result Summary
resultsMetExpectations: Results of the run met expectations?
resultsSummary: Results Summary
retry: Retry
retryOptional: Retry (Optional)
revertSchedule: Revert Schedule
revertScheduleText: Enabling this will make the schedule to revert after completion.
role: Role
run: Run
runAllExperiment: Run All Experiments
runAt: Run at
runCommand: Step 2 - Run the command
runCommands: Please copy and run the following command in your command prompt.
runCreatedOn: Run created on
runCreatedSuccessfully: Run created successfully
runDailyAt: Run daily at
runDetails: Run Details
runEvery: Run every
runHistory: Run History
runLogsNotAvailableYet: Please wait until the faults have started to access the logs.
runMarkedAsCompleted: Run marked as completed
runNow: Run Now
runOn: Run on
runOnSpecificDay: Run on a specific day at monthly interval
runOnSpecificDayMonth: Run on a specific day and month
running: Running
runs: Runs
save: Save
saveAndContinue: Save & Continue
saveToChaosHub: Save to ChaosHub
saveToChaosHubSuccess: Successfully pushed experiment to ChaosHub
saveValues: Save Values
schedule: Schedule
scheduleType: Schedule Type
scheduledBy: Scheduled by
scheduledFor: Scheduled for
scope: Scope
search: Search
searchExperimentRunID: Search for Experiment Run ID
searchExperiments: Search Experiments
searchForAProbe: Search For a Probe
searchForChaosFaults: Search for Chaos Faults
searchForHub: Search for a hub
searchForMonitoredServices: Search for a monitored service
searchHub: Search for a Hub
secret: Secret
securityKeyType: Select Security Key Type
seeAllChaosHubs: See All ChaosHubs
seeAllChaosInfrastructures: See All Infrastructures
seeAllEnvironments: See All Environments