Skip to content

Cluster deployments with helm charts with different name space other than "crapi" fails #361#362

Merged
piyushroshan merged 1 commit intoOWASP:developfrom
Abhishek2271:develop
Feb 15, 2026
Merged

Cluster deployments with helm charts with different name space other than "crapi" fails #361#362
piyushroshan merged 1 commit intoOWASP:developfrom
Abhishek2271:develop

Conversation

@Abhishek2271
Copy link
Copy Markdown
Contributor

Description

Please include a summary of the change, motivation and context.

on a bugfix: This change intends to fix issue #361

Due to hardcoded namespace values, crAPI deployments to clusters were not working when the namespce is other than "crAPI". Helm charts should never have hardcoded values. This is a simple fix that is tested locally.

Testing

In place of hardcoded values for the namespace, the namespace is dynamically specified based on the helm install.

Hardcoded "crapi" for namespace was replaced with {{ .Release.Namespace }}

This was tested by deploying crAPI using Helm onto an EKS cluster.

Checklist:

Only three files are changed: role.yaml, rolebindings.yaml and values.yaml.

@Abhishek2271 Abhishek2271 changed the title Custer deployments with helm charts with different name space other than "crapi" fails #361 Cluster deployments with helm charts with different name space other than "crapi" fails #361 Feb 15, 2026
@piyushroshan piyushroshan merged commit 55c81ad into OWASP:develop Feb 15, 2026
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