This is an automated email from the ASF dual-hosted git repository.

hanahmily pushed a change to branch fix/validate-resource-name-lengths
in repository https://gitbox.apache.org/repos/asf/skywalking-banyandb-helm.git


 discard a2ac24a  Validate generated resource names to avoid Kubernetes 63-byte 
limit errors
    omit 0cfe134  Release v0.6.0
     add 4832cea  Remove all etcd compoments (#61)
     add 3e8d471  Prepare for next development cycle (#62)
     add 8f1b27f  Enable FODC panic/crash diagnostics collection (#63)
     add 70487a5  disable the lifecycle metrics collector if the container has 
disabled (#64)
     add 0cb1a64  Add FODC memory-pressure pprof capture for data and liaison 
nodes (#65)
     add cc2530d  Prepare for release 0.7.0-rc0 (#66)
     add 8ab58e8  Validate generated resource names to avoid Kubernetes 63-byte 
limit errors

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (a2ac24a)
            \
             N -- N -- N   refs/heads/fix/validate-resource-name-lengths 
(8ab58e8)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .github/workflows/e2e.ci.yaml                      |   8 +-
 CHANGES.md                                         |  14 ++
 README.md                                          |  28 ----
 chart/Chart.yaml                                   |   2 +-
 chart/templates/_helpers.tpl                       | 112 +++++---------
 chart/templates/cluster_data_statefulset.yaml      |  81 ++++++++---
 chart/templates/cluster_liaison_statefulset.yaml   |  68 +++++++--
 chart/templates/cluster_ui_deployment.yaml         |  21 ---
 chart/templates/node_discovery_file_configmap.yaml |   2 +-
 chart/templates/standalone_statefulset.yaml        |  34 ++++-
 chart/values-lifecycle.yaml                        |  73 +++-------
 chart/values.yaml                                  |  85 ++++-------
 doc/parameters.md                                  |  99 ++++++-------
 .../{e2e-etcd-cluster.yaml => e2e-cluster.yaml}    |  19 +--
 test/e2e/e2e-dns-node-etcd-schema-cluster.yaml     | 161 ---------------------
 test/e2e/e2e-dns-node-native-schema-cluster.yaml   | 144 ------------------
 test/e2e/e2e-fodc-proxy-service.yaml               |  17 ---
 test/e2e/e2e-lifecycle.yaml                        |  17 ---
 test/e2e/setup-e2e-shell/install-etcdctl.sh        |  38 -----
 ...alues.etcd-cluster.yaml => values.cluster.yaml} |  22 +--
 test/e2e/values.dns-cluster-state.yaml             |   2 +-
 test/e2e/values.dns-node-etcd-schema-cluster.yaml  |  94 ------------
 .../e2e/values.dns-node-native-schema-cluster.yaml |  79 ----------
 test/e2e/values.fodc.yaml                          |  15 +-
 test/e2e/values.lifecycle.yaml                     |  27 ++--
 test/e2e/values.standalone.yaml                    |   2 +-
 26 files changed, 317 insertions(+), 947 deletions(-)
 rename test/e2e/{e2e-etcd-cluster.yaml => e2e-cluster.yaml} (96%)
 delete mode 100644 test/e2e/e2e-dns-node-etcd-schema-cluster.yaml
 delete mode 100644 test/e2e/e2e-dns-node-native-schema-cluster.yaml
 delete mode 100644 test/e2e/setup-e2e-shell/install-etcdctl.sh
 rename test/e2e/{values.etcd-cluster.yaml => values.cluster.yaml} (96%)
 delete mode 100644 test/e2e/values.dns-node-etcd-schema-cluster.yaml
 delete mode 100644 test/e2e/values.dns-node-native-schema-cluster.yaml

Reply via email to