The access token is not displayed correctly in confirmation emails about kubernetes HOT 4 CLOSED

Please provide more information on the installation method that you've used.
Is it the installation via the platform Marketplace, or via a JPS manifest, or something else?

from kubernetes.

When I install (via the jelastic API) the manifest of kubernetes from branch v1.25.4, then the token doesn't display correctly in the confirmation email. When I install kubernetes from the marketplace the token looks good in the confirmation email (though I'd have to try again to be sure). I am using jelastic v8.1.1.

from kubernetes.

I have deployed the k8s cluster this morning in two different ways:

• through the install method documented here and with this manifest: in the email, the token is displayed as I showed in my initial post, i.e. with html tags
• through the marketplace in the jelastic dashboard, with version 1.25.4: the token is displayed nicely in the confirmation email

from kubernetes.

It is the expected behavior for the manifests installed not from the platform Marketplace.
For the security reasons, some of visual elements and functionality are restricted for external manifests, that are installed via API or in Dashboard (via "Import" option).
To get the behavior, provided by native Marketplace manifests, you need to publish the manifest to the platform's Marketplace.

from kubernetes.