Conversation
orch-configs/templates/cluster.tpl
Outdated
| {{- if .Values.enableDefaultTraefikRateLimit }} | ||
| - orch-configs/profiles/default-traefik-rate-limit.yaml | ||
| {{- end }} | ||
| {{- if .Values.enableEIMvPROOnly }} |
There was a problem hiding this comment.
Where is this parameter enableEIMvPROOnly set?
There was a problem hiding this comment.
This should be set in some preset file, similar to what we have in https://github.com/open-edge-platform/scorch/blob/main/presets/dev-coder.yaml , then deployment is started with mage deploy:kindPreset my-preset-file.yaml . Also the profile could be added to a new cluster configuration for modular vpro in https://github.com/open-edge-platform/edge-manageability-framework/tree/main/orch-configs/clusters - if we are going to have one.
There was a problem hiding this comment.
OK setting scenario to vpro can be done in the common profile for modular vpro - such as in this PR : https://github.com/open-edge-platform/edge-manageability-framework/pull/1320/changes#diff-f993c15d5bc8ac484c3bda4b8532fee69481771b57cdb8cec21e39bdbda86f36R9
| {{- end }} | ||
| {{- if .Values.enableEIMvPROOnly }} | ||
| - orch-configs/profiles/enable-eim-vpro-only.yaml | ||
| {{- end }} |
There was a problem hiding this comment.
We need to add this parameter enableEIMvPROOnly in the onprem tpl file as well
There was a problem hiding this comment.
added to generate_cluster_yaml.sh
2 participants
Description
This PR adds a new profile that allows for setting 'scenario' flag to 'vpro' in apiv2 helm chart.
Related PRs:
Fixes # (issue)
Any Newly Introduced Dependencies
Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: