This is to specifically ease the reviewing of healing related PRs. As we know, healing has more asynchronous decoupled tasks which we need to keep track to join our thoughts (specially during the review)

A design documentation, maybe with a design diagram would help to understand the process and differences between self-healing and admin-healing

Ideally we can keep track of the fore coming c

Is your feature request related to a problem? Please describe.

We plan to do ruling and alerting like Prom with Alertmanager, but in the meantime we have multiple ways to already alerts on logs and I think we should document it.

This include alerting with Promtail/Alertmanager using stages or alerting with Grafana using Loki as Prometheus datasource.

We should also explain that you

I see various references to bom in the build file, docs, etc. E.g. the docs say "The no longer used group for Graal is no longer part of the bom". I'm not sure what this means. It would be useful to add a definition for bom (I'm guessing it's not the definition I know of "byte order mark" 😉)

Source page: https://github.com/aws-samples/aws-workshop-for-kubernetes/tree/master/02-path-working-with-clusters/201-cluster-monitoring

Text with broken link: Deploying applications using Kubernetes Helm charts.

Link referred: https://github.com/aws-samples/aws-workshop-for-kubernetes/blob/master/03-path-application-development/306-app-management-with-helm

Fix suggestion: 306 to be repla

Bug Report

The [STREAM_TASK] configuration block was documented for v1.3, but I'm unable to find documentation for this in the v1.4 docs.

Many advanced K8s workload management features require the use of labels. In some cases, labels are needed after Pods are created so that adding them to Pod template does not help . For example,

• A canary release plan may want to upgrade X number of Pods out of Y number of total replica. We can add a label to the chosen Pod so that the rollout controller can upgrade these Pods first.

• Po

Just like we did for project proposals, we should have a pull request check list template to walk people through the annual review process.

Is this a BUG REPORT or FEATURE REQUEST?:
Create Profile with invalid storage dataType: FAIL (No proper hint message why it is failing. For Ex: if you see, it validates for name datatype)
root@server:~/opensds-installer/ansible# osdsctl profile create '{"name": "1235", "storageType": block}'
ERROR: invalid character 'b' looking

See https://github.com/mailgun/gubernator/blob/master/architecture.md#side-effects-of-global-behavior

It states: Using GLOBAL can increase the amount of traffic per rate limit request if the cluster is large enough

I assume that with 'the cluster' you mean the cluster of gubernator instances.

Can you give a more detailed indication what you mean with '_large'? Are we talking about te

可以将openebs升级到最新版本吗？当前是1.7.0 ，最新是1.9.0

[root@master01 ~]# helm search repo openebs
NAME            CHART VERSION   APP VERSION     DESCRIPTION                         
apphub/openebs  1.7.0           1.7.0           Containerized Storage for Containers

升级方法

helm repo add stable https://kubernetes-charts.storage.googleapis.com/

hlem search repo openebs

Some comments:

1. __tests__:
   1. some helpers defined in the test scripts do not seem to be used (ex loadUrl, waitForText, ...), are they necessary?
   2. nt4s url needs to be removed, this should preferably be a config variable somewhere (lib/config.js baseUrl?), you can use http://test.fadi.cetic.be as a placeholder.
   3. if possible, use the test case identifier in the file