Closed APIM-KiranVaddadi closed 1 year ago
@APIM-KiranVaddadi - env shouldn't be used directly in the job spec where they have to be declared in values.yaml (especially for db passwords).
The best option would be a config file that is mounted via an existingSecret - this allows use of the Secret Store CSI Driver and existing Kubernetes Secrets.
Its addressed now.
@APIM-KiranVaddadi - env shouldn't be used directly in the job spec where they have to be declared in values.yaml (especially for db passwords). The best option would be a config file that is mounted via an existingSecret - this allows use of the Secret Store CSI Driver and existing Kubernetes Secrets.
Its addressed now.
This looks like it requires gateway admin username/password? https://github.com/APIM-KiranVaddadi/apim-charts/blob/otk_install_job/charts/gateway/templates/otk-install-job.yaml
Is the management flag used to avoid ephemeral use cases?
@APIM-KiranVaddadi - env shouldn't be used directly in the job spec where they have to be declared in values.yaml (especially for db passwords). The best option would be a config file that is mounted via an existingSecret - this allows use of the Secret Store CSI Driver and existing Kubernetes Secrets.
Its addressed now.
This looks like it requires gateway admin username/password? https://github.com/APIM-KiranVaddadi/apim-charts/blob/otk_install_job/charts/gateway/templates/otk-install-job.yaml
Is the management flag used to avoid ephemeral use cases?
It does need username/password. Updated the job to get them from secret. Also removed the dependency on management to be enabled. The job needs only restman to be enabled.
Description of the change
Install OTK using a job
Benefits
Seamless installation and upgrade of OTK.
Drawbacks
Applicable issues
Additional information
Checklist
Chart.yaml
according to semver.[charts/gateway]
)values-production.yaml
apart fromvalues.yaml
, ensure that you implement the changes in both files