You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
vmatsiiako
changed the title
Option to configure hardcoded global configuration namespace
[ENG-120] Option to configure hardcoded global configuration namespace
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:infisical/k8-operator/controllers/infisicalsecret_helper.go
Line 25 in a255af6
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
The text was updated successfully, but these errors were encountered: