Upgrade SWCK to 0.10.0 and Horizon UI examples to horizon-0.6.0#189
Merged
Conversation
Bump chart/operator and chart/adapter to SWCK 0.10.0 (image tag now drops the v prefix to match what was published to Docker Hub). Refresh the operator CRDs from the v0.10.0 upstream, adding the new EventExporter CRD, and regenerate the manager-role ClusterRole with the matching permissions. Point CI at the released SWCK image and bump SWCK reference URLs in the e2e tests.
wankai123
approved these changes
Jun 8, 2026
apache/skywalking-ui:horizon-0.6.0 is the current published Horizon UI release; horizon-1.0.0 was an aspirational example that does not yet exist on Docker Hub.
- OAP: a0cec0c -> 2aa0e85 (CVE dependency bumps) - Horizon UI: 80565f5 -> 58a4c1f (post-v0.6.0, includes vitest CVE patch) - BanyanDB: 5dedaa1 -> 65d951f (fodc agent retry fix)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SWCK 0.10.0
chart/operatorandchart/adapterto SWCK0.10.0(the new release image dropped thevprefix on Docker Hub —apache/skywalking-swck:0.10.0).chart/operator/templates/crds.yamlfrom upstream v0.10.0, adding the newEventExporterCRD and theUI.spec.kinddiscriminator that picks between Horizon UI (default) and legacy Booster UI.ClusterRolefrom v0.10.0'srole.yaml, granting verbs oneventexporters(+/finalizers,/status); preserves the chart'ssigners/approvepatch.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).https://raw.githubusercontent.com/apache/skywalking-swck/v0.9.0/…(and the SHA-pinnede98e180…/…) references intest/e2e/swck/*.yamltov0.10.0— the referenced upstream fixtures are byte-identical, so this is purely a hygiene refresh.The local
test/e2e/swck/skywalking-components*.yamlfiles are intentional chart-specific overrides (placeholder substitution, dedicated namespace, inlineOAPServer.spec.configstorage wiring) — they remain schema-compatible with v0.10.0 CRDs, and the new defaultUI.spec.kind: horizonlines up with the Horizon UI image CI already uses.Horizon UI tag examples
horizon-1.0.0references inREADME.md,chart/skywalking/README.md, andchart/skywalking/values.yamlforhorizon-0.6.0.apache/skywalking-ui:horizon-0.6.0is the currently published Horizon UI release;horizon-1.0.0was an aspirational example that does not yet exist on Docker Hub.Test plan
helm lintclean forchart/adapter,chart/operator,chart/skywalking(with the three required values set).helm templaterenders 11 CRDs (10 existing + neweventexporters) and resolves the operator image todocker.io/apache/skywalking-swck:0.10.0.helm template chart/skywalking --set ui.image.tag=horizon-0.6.0renders with Elasticsearch+ECK and BanyanDB storage paths.