Closed KfreeZ closed 4 weeks ago
was it a typo chatqa versus chatqna?
@KfreeZ and team -- more of a discussion. I know this is a sample and we are making namespace optional -- good. But what will the default be? Why because if every chain goes into a namespace that reflects the chains purpose, there will be less service sharing. If each loggedin user comes with a user or group specific namespace, the logic there would be potentially for chargeback/billing.
@mkbhanda I am writing chatqa on purpose, for saving a letter to type :) But if you think chatqna is better, we can revert to it. with this change, the service defined in a same pipeline will by default live in same the namespace as where CR is created, if the optional namespace is set, it will be assigned to this specific optional namespace
Description
make "namespace" field of each resource in the CR optional, if it's not specifically defined, get the namespace in the context
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.
Dependencies
n/a
Tests
Remove all the namespace in the "chatqa.yaml" or "codegen.yaml", which is the customer defined resource. the controller bring up all the resource in the namespace where the CR is installed.