Skip to content

Conversation

@mblaze-da
Copy link
Contributor

@mblaze-da mblaze-da commented Dec 12, 2025

fixes https://github.com/DACH-NY/canton-network-internal/issues/2791

I am not very confident about these changes. I had some difficulties figuring out the sequencer hostname and I'm still not 100% sure I got it right. I'm also not sure if my assumptions about how to iterate through SVs and migrations are correct.

@mblaze-da mblaze-da marked this pull request as draft December 12, 2025 13:29
return [
...(function* () {
for (const migration of DecentralizedSynchronizerUpgradeConfig.runningMigrations()) {
for (const sv of coreSvsToDeploy) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not allSvsToDeploy? I guess it doesn't matter for MainNet (only core SVs there), but for consistency?

namespace: ingressNs.metadata.name,
},
spec: {
host: `${sequencerName}.${ingressName}.svc.cluster.local`,
Copy link
Contributor

@martinflorian-da martinflorian-da Dec 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be clear: The intention here is to use k8s-internal addresses, not the external one we define via VirtualService?

If so... can't you just check on a scratchnet cluster or CILR if you got the hostname right? I'd launch a shell on some validator pod and try reaching the endpoint from there via curl or grpcurl.

(Not very confident about the networking stuff here myself...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants