You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs(pm): point ManagedProvider config at published v0.0.7 charts (#669)
* docs(pm): bump ManagedProvider chart references to v0.0.7
The provider-quickstart Helm charts are now published at v0.0.7 under
ghcr.io/platform-mesh/provider-quickstart/charts (first release including the
publish-helm CI job from #668). Point the config/pm ManagedProvider manifest
and docs at the published version.
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
* feat(pm): pin kcp front-proxy via hostAliases, IP set through kustomize
The wildwest-controller's endpoint watcher dials the APIExport virtual-workspace
URL (https://root.kcp.localhost:8443/...) directly. Inside the pod that hostname
resolves to 127.0.0.1, so the watch fails with connection refused.
Enable common.hostAliases on the controller to pin *.kcp.localhost to the
in-cluster front-proxy service. The ClusterIP is environment-specific, so it is
exposed as the single editable field via a kustomize JSON patch in
kustomization.yaml rather than hardcoded in the manifest.
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
* feat(pm): deploy wildwest-armament-sync via ManagedProvider
Add the armament syncer as a third runtimeDeployments component. It connects to
kcp through the provider workspace kubeconfig, so it gets the same
wildwest-provider-kubeconfig override and *.kcp.localhost hostAliases pinning as
the controller; the front-proxy IP is patched for both via kustomization.yaml.
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
* ci: build and publish the armament-sync image
The wildwest-armament-sync chart referenced
ghcr.io/platform-mesh/provider-quickstart-armament-sync, but no CI job ever built
that image, so deploying the chart fails with ImagePullBackOff.
Add a build-armament-sync job (mirroring build-controller, using
deploy/armament-sync.Dockerfile) and gate publish-helm on it. Default the chart's
image.tag to the appVersion so the released chart (packaged with
--app-version=<release tag>) pulls the matching image tag the job publishes.
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
---------
Signed-off-by: Mangirdas Judeikis <mangirdas@judeikis.lt>
0 commit comments