Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENG-120] Option to configure hardcoded global configuration namespace #1023

Open
6ixfalls opened this issue Sep 24, 2023 · 0 comments
Open
Labels
🚀 feature request New feature or request k8-operator Related to k8-operator

Comments

@6ixfalls
Copy link

6ixfalls commented Sep 24, 2023

Feature description

There should be an option to change the namespace where the infisical-config ConfigMap for the Secrets Operator is searched for. Currently, the value infisical-operator-system is hardcoded:

const OPERATOR_SETTINGS_CONFIGMAP_NAMESPACE = "infisical-operator-system"

Why would it be useful?

The operator documentation doesn't even specify that the chart should be deployed in the infisical-operator-system namespace, and the only thing that it says should be in the namespace is the ConfigMap. It would be logical to have the configuration secret reside in the same namespace as the chart.

From SyncLinear.com | ENG-120

@vmatsiiako vmatsiiako changed the title Option to configure hardcoded global configuration namespace [ENG-120] Option to configure hardcoded global configuration namespace Sep 24, 2023
@akhilmhdh akhilmhdh added 🚀 feature request New feature or request k8-operator Related to k8-operator labels Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 feature request New feature or request k8-operator Related to k8-operator
Projects
None yet
Development

No branches or pull requests

2 participants