We have to ensure, that the ACM documentation covers also the Open Source use case, also consdering the case that Compass is used by the ACM.
Following points have to be adjusted:
Warnings hints about missing Compass Runtime Agent in ACM are obsolete: we have the Compass runtime agent now integrated into the ACM module.
We have to point out that Istio is required (but also making clear, that it's not mandatory for customers to use to the Kyma Istio module) because ACM needs an Istio gateway resource.
We have some customers who run Compass Director by themself: for such cases we have to explain how an integration with AC is possible, even without Compass Manager (by providing a proper secret)
ACM is currently expecting an Gardener cluster as runtime which isn't the case for OS users usually. We have to point out, that a shoot-info config map has to be created by the customer which includes the domain-name of the cluster. If the config map is missing, ACM will fail because it could not find the domain name.
Area
Application Connector
Reasons
Docs are not fully in sync with latest changes introduced by ACM module.
Description
We have to ensure, that the ACM documentation covers also the Open Source use case, also consdering the case that Compass is used by the ACM.
Following points have to be adjusted:
shoot-infoconfig map has to be created by the customer which includes the domain-name of the cluster. If the config map is missing, ACM will fail because it could not find the domain name.Area
Reasons
Docs are not fully in sync with latest changes introduced by ACM module.
Assignees
@kyma-project/technical-writers
Attachments