Skip to content

feat: adapted idhub and issuer-service helm configurations#1

Open
saudkhan116 wants to merge 1 commit into
developfrom
feat/helm-chart-config
Open

feat: adapted idhub and issuer-service helm configurations#1
saudkhan116 wants to merge 1 commit into
developfrom
feat/helm-chart-config

Conversation

@saudkhan116

@saudkhan116 saudkhan116 commented Apr 8, 2026

Copy link
Copy Markdown

WHAT

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

  • Updated ConfigMap names to include nameOverride prefix and remove hardcoded values to enable multiple idhub instances
    • from identityhub-datasource-config to {{ $fullName }}-identityhub-datasource-config
    • from identityhub-config to {{ $fullName }}-identityhub-config
  • Updated deployment template to allow dynamic ConfigMap names
    • name: {{ printf "%s-%s" $fullName $value | quote }}
  • Added seed jobs to inject the certificates to the vault
  • Adapted helm vaules files: values-stag-ihub-consumer.yaml, values-stag-ihub-provider.yaml and values-stag-issuer.yaml
  • The following docker images have been used:
    • IDHUB: registry.onstackit.cloud/constructx/identityhub-dev
    • ISSUER: registry.onstackit.cloud/constructx/issuerservice-dev

WHY

Briefly state why the change was necessary.

There is a need to demonstrate the running Identityhub and Issuer Service to perfrom e2e data exchange in Construct-X ecosystem.

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:25
@saudkhan116 saudkhan116 self-assigned this Apr 8, 2026
@saudkhan116 saudkhan116 added the feature A new feature request label Apr 8, 2026

@sb-embeteco sb-embeteco left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I have tested issuerservice and identityhub Helm deployments with both consumer and provider configurations. All deployments work with the Helm deployments from the Construct-X EDC Helm-Chart PR, and I was able to execute the transaction flow from the Testbed Bruno collection using them.

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.
  • We should include a note in the README files stating that the Tractus-X Helm repository should not be used for the Construct-X deployment, and that the new values files must be explicitly selected using the -f flag in the helm install command.

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.

port: 9292
path: /api/sts

didweb:

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

identityhub.didweb.https Block is not mentioned in README.

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