Skip to content

Support for installing Sweet Security via pulumi - #6989

Open
isegall-da wants to merge 4 commits into
mainfrom
isegall/sweet
Open

Support for installing Sweet Security via pulumi#6989
isegall-da wants to merge 4 commits into
mainfrom
isegall/sweet

Conversation

@isegall-da

@isegall-da isegall-da commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

For now, disabled by default. Tested on a scratchnet, seems to work fine.

Part of https://github.com/DACH-NY/canton-network-internal/issues/6624

Pull Request Checklist

Cluster Testing

  • If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If an upgrade test is required, comment /upgrade_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
  • If a logical synchronizer upgrade test is required (from canton-3.5), comment /lsu_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

  • Include any change that might be observable by our partners or affect their deployment in the release notes.
  • Specify fixed issues with Fixes #n, and mention issues worked on using #n
  • Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

  • Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
.
Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
Signed-off-by: Itai Segall <itai.segall@digitalasset.com>
Signed-off-by: Itai Segall <itai.segall@digitalasset.com>

@martinflorian-da martinflorian-da left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Let's make this configurable so we have more control about which networks we deploy this to and when 🙏


configureReloader();

configureSweet();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Shall we make this configurable? Unlike reloader you (AFAIU) need to pay to be able to use it, so including that without an option to disable (on the public repo) seems a bit weird.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

...and also you might want to stagger the deployment so you don't risk breaking all (ci) networks at the same time?

} from '@canton-network/splice-pulumi-common';

export function configureSweet(): k8s.helm.v3.Release {
const operatorNs = exactNamespace('sweet-operator', false, true);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Any reason not to use the same namespace for both?


export function configureSweet(): k8s.helm.v3.Release {
const operatorNs = exactNamespace('sweet-operator', false, true);
const sweetNs = exactNamespace('sweet', false, true);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why retainOnDelete = true? On both namespaces?

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.

2 participants