Zheng Xi Zhou

ct lint passed a chart which failed in helm lint verification

3

**Is this a request for help?**: No. --- **Is this a BUG REPORT or FEATURE REQUEST?** (choose one): **Version of Helm and Kubernetes**: /charts/submitted/redis-operator # helm version Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4",...

Learnt from issue #15, deprecated Chart aws-cluster-autoscaler should NOT be found in AppHub. Please help confirm this. Thanks. ``` helm install aws-cluster-autoscaler apphub/aws-cluster-autoscaler NAME: aws-cluster-autoscaler LAST DEPLOYED: 2019-07-01 17:08:30.696557 +0800...

Any need to test submitted Charts before synchronizing?

3

Is there any need to test use submitted Charts before they are to be synchronized to `AppHub`? If so, I think I can provide - static verification: like helm lint/template...

What's the differences between charts from curated and those from stable/incubator of https://github.com/helm/charts? I found the number and version of Charts differs a lot. Thanks.

`acs-engine-autoscaler` could not be found by `helm search`

3

``` ➜ /Users/zhouzhengxi helm repo list NAME URL incubator https://kubernetes-charts-incubator.storage.googleapis.com/ apphub https://apphub.aliyuncs.com stable https://kubernetes-charts.storage.googleapis.com/ ➜ /Users/zhouzhengxi helm search acs-engine-autoscaler NAME CHART VERSION APP VERSION DESCRIPTION stable/acs-engine-autoscaler 2.2.2 2.1.1 DEPRECATED Scales...

Could the authority of project `AppHub Roadmap` be granted to me?

1

I notice that you use `Github project` to manage features/bugs, I wonder if I could be granted this authority then I can open them in that way. Thanks.

`云原生应用中心` 想法超赞：） 我有一个小问题，Chart 可能发布到不同的区域，那么可能需要维护不同 docker registry (`gcr.io`，`quay.io`)的 Chart，是否能在 `helm add repo` 时提供选项，如 `--use-community-repo` - 直接添加`hub.helm.sh` repo，在 Chart 这一层保持与社区 repo 完全不变 - 提示用户添加阿里云镜像加速器`https://yq.aliyun.com/articles/29941` 这样用户可以无感、告诉使用社区 Chart 和该 Chart 的镜像。 但是，这里有一个问题，`helm add repo`...

Workload Labeling Proposal

2

to recommend a simple way - Workload Labeling, to easily establish connections between Workloads, Components, AppConfigurations, and pods. Signed-off-by: Zheng Xi Zhou

[Feature] Propagate labels of non-core workloads to pod template

5

**Is your feature request related to a problem? Please describe.** In order to implement feature https://github.com/crossplane/oam-kubernetes-runtime/issues/174, not only could labels of ContainerizedWorkloads be propagated to its pods (implemented in https://github.com/crossplane/oam-kubernetes-runtime/pull/175),...

Support list/slic type of user defined workloadRef path

3

Workload will be applied to trait CR to its path `spec.workloadRef` in proposal [trait-workload-interaction-mechanism](https://github.com/crossplane/oam-kubernetes-runtime/blob/master/design/one-pager-trait-workload-interaction-mechanism.md#proposal). If the path mechanism support user defined list/slic type `spec.gateways[0]` as below? ``` apiVersion: core.oam.dev/v1alpha2 kind:...