Skip to content

feat: adapted construct-x connector helm chart configurations#5

Open
saudkhan116 wants to merge 2 commits into
developfrom
feat/conn-helm-chart
Open

feat: adapted construct-x connector helm chart configurations#5
saudkhan116 wants to merge 2 commits into
developfrom
feat/conn-helm-chart

Conversation

@saudkhan116
Copy link
Copy Markdown

@saudkhan116 saudkhan116 commented Apr 8, 2026

WHAT

Briefly describe what your PR changes, which features it adds/modifies.

  • Adapted the controlplane and dataplane templates
  • Added seed jobs to inject certificates to the vault
  • Updated helm values files; values-consumer.yaml and values-provider.yaml
  • The following docker images have been used:
    • Controlplane: registry.onstackit.cloud/constructx/con-x-controlplane-postgresql-hashicorp-vault
    • Dataplane: registry.onstackit.cloud/constructx/con-x-dataplane-postgresql-hashicorp-vault

WHY

Briefly state why the change was necessary.

To demonstrate data exchange using Construct-X connectors and ensure compatibility between IdentityHub, Issuer-service and portal registration service.

FURTHER NOTES

List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.

Closes # <-- insert Issue number if one exists

@saudkhan116 saudkhan116 requested a review from mhellmeier April 8, 2026 15:34
@saudkhan116 saudkhan116 self-assigned this Apr 8, 2026
@saudkhan116 saudkhan116 added the feature A new feature request label Apr 8, 2026
@mhellmeier mhellmeier requested a review from eschrewe April 9, 2026 14:16
@mhellmeier mhellmeier requested a review from snoeffels April 30, 2026 06:47
Copy link
Copy Markdown

@sb-embeteco sb-embeteco left a comment

Choose a reason for hiding this comment

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

Both deployment options (consumer and provider) worked on my cluster using the deployments from the Construct-X IdentityHub Helm chart PR; see the PR comment in the IdentityHub repository.

Questions:

  • Would the deployment using the legacy values file and Tractus-X container still work after the deployment files have been updated to use the Conststruct-X EDC Testbed Container? If not, we might want to consider opening a separate Chart for the Con-X Testbed and restore the Tractus-X Chart.

Notes:

  • Since I'm using Istio as the ingress controller on my cluster, I wasn't able to explicitly test the ingress block in the values files. However, I don't think the changes to the configuration will have a negative impact on the deployment.
  • The README can no longer be fully applied to the new deployment and should be updated to reflect using the new values files.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This File is missing a License Header.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This File is missing a License Header.

controlplane:
nameOverride: "consumer-conn-controlplane"
fullnameOverride: ""
enabled: true
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

controlplane.nameOverride, controlplane.fullnameOverride and controlplane.enabled do not appear to have been implemented yet. The same applies to these keys in dataplane block and the corresponding entries in the provider values file.

port: 9030
# -- path for incoming api calls
path: /validation
# -- dsp api, use
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

NIT: wrong comments in line 194 and 200. Same applies to provider values file.

- default
- protocol
- management
- dsp
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

controlplane.ingresses[0].endpoints dsp endpoint not configured in controlplane.endpoints. Also applies to provider values file.

port: 9510
# -- path for incoming api calls
path: /management
# -- authentication key, must be attached to each request as `X-Api-Key` header
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

NIT: comment implies authKey. Also applies to provider values file.

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

Labels

feature A new feature request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants