Release notes and documentation updates for Mendix on Kubernetes v2.27.0 (planned for release on June 1)#11260
Release notes and documentation updates for Mendix on Kubernetes v2.27.0 (planned for release on June 1)#11260zlogic wants to merge 13 commits into
Conversation
Copy-pasting "uses some labels for internal use" when it should've been changed to "uses some annoattions for internal use".
|
@Nidhi251289 @walkline If there are any changes in the release schedule, please let the documentation team know, to help with scheduling and priorities. |
Nidhi251289
left a comment
Nidhi251289
left a comment
There was a problem hiding this comment.
operator release review comments
| Gateway API is the successor to the Ingress API. Gateway API splits configuration across different roles: | ||
|
|
||
| * _cluster operators_ manage **Gateway** resources, configuring central rules and policies such as TLS and IP filtering; | ||
| * _application developers_ manage **HTTPRoute** resources, specifying confuguration relevant for a specific destination, such as a Mendix app environment. |
There was a problem hiding this comment.
can u fix the spelling for configuration
| * In the **Gateway Route Parent Reference**, specify settings for the HTTPRoute's [parentRefs](https://gateway-api.sigs.k8s.io/reference/api-spec/1.4/spec/#parentreference). This would typically be a Gateway resource configured by a cluster admin. | ||
| * **Group** specifies the ParentReference `group` value (usually `gateway.networking.k8s.io`). | ||
| * **Kind** specifies the ParentReference `kind` value (usually `Gateway`). | ||
| * **Name** and **Namespace** specify the existing ParentReference's Kubernetes name and namespace. |
There was a problem hiding this comment.
Should we specify that the namespace where the gateway is installerd
There was a problem hiding this comment.
In this case, it's a bit more complicated:
- the Gateway itself (the Helm chart or OpenShift Operator) can be installed in one namespace
- the Gateway CR can be created in another namespace
- and the Parent Reference can also be some other object type, for example a ListerSet (instead of a Gateway).
In my opinion, a cluster admin who wants to use a Gateway (instead of an Ingress) should be aware what a ParentReference means, and use the Gateway implementation's official examples and documentation to understand what exactly needs to be specified in the ParentReference. It usually depends on the exact cluster setup.
| "X-request-header-3": "example-value-3" | ||
| "X-request-header-4": "example-value-4" | ||
| remove: | ||
| # Remove the following headers |
There was a problem hiding this comment.
Should we specify that the above additional settings are not possible to add via mx-ops-cli currently
| * We have added an option to load client certificates from Kubernetes secrets created on the cluster side. | ||
| * We have added an option to specify default `nodeSelectors` for pods created and managed by the Operator. | ||
| * We have added an option to specify default labels for pods created and managed by the Operator. | ||
| * We have addressed and issue where enabling OpenTelemetry auto-instrumentation would show a "processing" spinner on the Runtime status. |
There was a problem hiding this comment.
addressed an issue, replace and with an
| * We have added an option to specify default labels for pods created and managed by the Operator. | ||
| * We have addressed and issue where enabling OpenTelemetry auto-instrumentation would show a "processing" spinner on the Runtime status. | ||
| * We have updated components to use the latest dependency versions in order to improve security score ratings for container images. | ||
| * We have updated the list of supported platforms to include Kubernetes 1.36. |
There was a problem hiding this comment.
Should we also add that we allow to add custom domain in Openshift
Also, should we add the improvements done on ops-cli side
There was a problem hiding this comment.
I didn't document any changes for the mx-ops-cli in this PR.
katarzyna-koltun-mx
left a comment
katarzyna-koltun-mx
left a comment
There was a problem hiding this comment.
Reviewed and waiting for the go ahead.
4 participants
This MR contains release notes for the new Mendix Operator version, as well as documentation for new features:
In content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md, removed a section that duplicated https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/private-cloud-ingress-settings/.
If there are no roadblocks in the release process, we're planning to publish this new version on June 1.