wu-sheng opened a new pull request, #189: URL: https://github.com/apache/skywalking-helm/pull/189
## Summary - Bump `chart/operator` and `chart/adapter` to SWCK `0.10.0` (the new release image dropped the `v` prefix on Docker Hub — `apache/skywalking-swck:0.10.0`). - Refresh `chart/operator/templates/crds.yaml` from upstream v0.10.0, adding the new `EventExporter` CRD and the `UI.spec.kind` discriminator that picks between Horizon UI (default) and legacy Booster UI. - Regenerate the manager-role `ClusterRole` from v0.10.0's `role.yaml`, granting verbs on `eventexporters` (+ `/finalizers`, `/status`); preserves the chart's `signers/approve` patch. - Point the e2e CI operator image at the released `docker.io/apache/skywalking-swck:0.10.0` (no longer needs the dev SHA workaround that was in place while waiting for Horizon UI support to ship). - Refresh `https://raw.githubusercontent.com/apache/skywalking-swck/v0.9.0/…` (and the SHA-pinned `e98e180…/…`) references in `test/e2e/swck/*.yaml` and `.claude/` allowlists to `v0.10.0` — the referenced upstream fixtures are byte-identical, so this is purely a hygiene refresh. The local `test/e2e/swck/skywalking-components*.yaml` files are intentional chart-specific overrides (placeholder substitution, dedicated namespace, inline `OAPServer.spec.config` storage wiring) — they remain schema-compatible with v0.10.0 CRDs, and the new default `UI.spec.kind: horizon` lines up with the Horizon UI image CI already uses. ## Test plan - [x] `helm lint` clean for `chart/adapter`, `chart/operator`, `chart/skywalking`. - [x] `helm template` renders 11 CRDs (10 existing + new `eventexporters`) and resolves the operator image to `docker.io/apache/skywalking-swck:0.10.0`. - [x] `helm template chart/skywalking` renders with Elasticsearch+ECK and BanyanDB storage paths. - [ ] CI e2e suite passes (Elasticsearch, BanyanDB standalone, BanyanDB cluster, and the four SWCK matrix entries). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
