Kk cloud foundry #9353
Kk cloud foundry #9353
Conversation
MarkvanMents
left a comment
MarkvanMents
left a comment
There was a problem hiding this comment.
@katarzyna-koltun-mx
I've made a couple of comments here. But generally looks good.
| Mendix Cloud deployments are also dependent on the latest version of the [Mendix Cloud Foundry Buildpack](https://github.com/mendix/cf-mendix-buildpack). The [Mendix Cloud Foundry Buildpack release notes](https://github.com/mendix/cf-mendix-buildpack/releases) are published separately, as other deployment targets are also dependent on the buildpack. | ||
|
|
There was a problem hiding this comment.
Is there the equivalent for Kubernetes, or is it completely hidden from customers?
There was a problem hiding this comment.
We had a discussion on how to do this. The Mendix Cloud platform has several platform components that will be updated regularly as well. We want to allow customers to track the updates of these platform components and "pin" their deployments to specific versions, so that they get the exact same experience across environments.
If we do this, it would make sense to give customers insight into changes between the platform component versions. And that means we need to publish release notes somewhere. Still under discussion what would be the best place for that, as the teams expect frequent, small releases.
There was a problem hiding this comment.
We could add a new set of release notes, or just add them to Mendix Cloud release notes.
The reason they were separate for M2ee is that M2ee is used by other sorts of deployment as well. If this is purely Mendix Cloud, then I would suggest adding them to the Mx Cloud release notes.
There was a problem hiding this comment.
Release notes are an open question, publishing as is for now.
There was a problem hiding this comment.
Don't forget to copy to Mx11 branch!
There was a problem hiding this comment.
Tbr with the Mx11 branch.
feddovanede
left a comment
feddovanede
left a comment
There was a problem hiding this comment.
Most of it looks good to me! Left some comments.
content/en/docs/deployment/mendix-cloud-deploy/environments-details-new.md
Outdated
Show resolved
Hide resolved
| | `permissions-policy: interest-cohort=()` | Exclude from Federated Learning of Cohorts (FLoC) calculation | | ||
| | `strict-transport-security` | TLS terminating webservers – set to `max-age=31536000` (365 days, in seconds)| | ||
| | `x-vcap-request-id` | Cloud Foundry to track requests through CF | | ||
| | `X-Request-ID` | Kubernetes to track requests through CF | |
There was a problem hiding this comment.
Same here:
Kubernetes to track requests through CF
should be
Kubernetes to track requests through Kubernetes
or
Kubernetes to track requests through the Mendix Cloud platform
content/en/docs/deployment/mendix-cloud-deploy/monitoring-with-apm/_index.md
Show resolved
Hide resolved
| Mendix Cloud deployments are also dependent on the latest version of the [Mendix Cloud Foundry Buildpack](https://github.com/mendix/cf-mendix-buildpack). The [Mendix Cloud Foundry Buildpack release notes](https://github.com/mendix/cf-mendix-buildpack/releases) are published separately, as other deployment targets are also dependent on the buildpack. | ||
|
|
There was a problem hiding this comment.
We had a discussion on how to do this. The Mendix Cloud platform has several platform components that will be updated regularly as well. We want to allow customers to track the updates of these platform components and "pin" their deployments to specific versions, so that they get the exact same experience across environments.
If we do this, it would make sense to give customers insight into changes between the platform component versions. And that means we need to publish release notes somewhere. Still under discussion what would be the best place for that, as the teams expect frequent, small releases.
MarkvanMents
left a comment
MarkvanMents
left a comment
There was a problem hiding this comment.
Responded to some of the comments with my thoughts. But eventually down to Kasia and Feddo to agree between them.
| Mendix Cloud deployments are also dependent on the latest version of the [Mendix Cloud Foundry Buildpack](https://github.com/mendix/cf-mendix-buildpack). The [Mendix Cloud Foundry Buildpack release notes](https://github.com/mendix/cf-mendix-buildpack/releases) are published separately, as other deployment targets are also dependent on the buildpack. | ||
|
|
There was a problem hiding this comment.
We could add a new set of release notes, or just add them to Mendix Cloud release notes.
The reason they were separate for M2ee is that M2ee is used by other sorts of deployment as well. If this is purely Mendix Cloud, then I would suggest adding them to the Mx Cloud release notes.
No description provided.