Is your feature request related to a problem? Please describe.
Some roles (like applications, keycloak) are mapped (in configuration/feature-mappings doc) by default to kubernetes_master component. When mode with k8s_as_cloud_service is used there is no kubernetes_master component so the mappings are not active. As a consequence vars for the mapped roles are not generated by epicli and thus deployment fails. To workaround this, one can map mentioned roles to any other component with count > 0.
Describe the solution you'd like
epicli generates vars for defined set of roles when k8s_as_cloud_service is true even if those roles are not mapped to any active component (with count > 0) but they are enabled in configuration/features doc. Furthermore, in such case they can be added to Ansible inventory with IP 127.0.0.1 (kubectl and helm will use SSH tunnel).
Describe alternatives you've considered
n/a
Additional context
n/a
DoD checklist
Changelog
[ ] updated
[ ] not needed
COMPONENTS.md
[ ] updated
[ ] not needed
Schema
[ ] updated
[ ] not needed
Backport tasks
[ ] created
[ ] not needed
Documentation
[ ] added
[ ] updated
[ ] not needed
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)
[ ] apply
[ ] upgrade
[ ] backup/restore
[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
Is your feature request related to a problem? Please describe. Some roles (like
applications,keycloak) are mapped (inconfiguration/feature-mappingsdoc) by default tokubernetes_mastercomponent. When mode withk8s_as_cloud_serviceis used there is nokubernetes_mastercomponent so the mappings are not active. As a consequence vars for the mapped roles are not generated by epicli and thus deployment fails. To workaround this, one can map mentioned roles to any other component withcount> 0.Describe the solution you'd like epicli generates vars for defined set of roles when
k8s_as_cloud_serviceis true even if those roles are not mapped to any active component (with count > 0) but they are enabled inconfiguration/featuresdoc. Furthermore, in such case they can be added to Ansible inventory with IP127.0.0.1(kubectlandhelmwill use SSH tunnel).Describe alternatives you've considered n/a
Additional context n/a
DoD checklist