This is just a warning due to latest HELM chart version update.

Step-by-step guide

According to dev team, the cockpit reaches the remote Magnolia using the Kubernetes proxy API.
The customers can use or not context root to host their application (/author for instance), the cockpit is then scanning the ingresses to determine whether the Magnolia instance is defined with a context root.

This issue happen due to the context path definition in your "values.yaml" and ingress didn't matched. So you need to configure your "values.xml" using for example "/author":

magnoliaAuthor:
  ...
  contextPath: /author

Then you should update the path of the ingress definition to "/author" like this:

ingress:
  ...
  hosts:
  - host: your-subdomain.your-domain.magnolia-platform.com
    paths:
    - instance: author
      path: /author


This information may change in the future due to PaaS product update or mechanism update.