Feat/v1.29.2 #245
Merged
Feat/v1.29.2 #245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…monitoring type This is a set of changes that allow the monitoring stack to be configured to send metrics to a remote Prometheus receiver, both with our current Prometheus monitoring type and with a new PrometheusAgent type that deploys a more minimal Prometheus intallation only for scraping and sending metrics. - Add `remoteWrite` section to prometheus' configuration in the scheam, so Prometheus can be set up to send metrics to a remote receiver. - Add prometheusAgent as monitoring type, as an alternative to prometheus+remoteWrite, allowing to have a "minimal" monitoring stack capable of sending metrics to a remote Prometheus receiver. Notice that this mode does not allow for querying the local Prometheus instance (so no local Grafana dashboards) or having local alerting set up. - Add migrations for switching between Prometheus and Prometheus Agent, and to and from `none`. - Update documentation with the new features
add a new customOutputs logging type that allows to choose where to ship the logs via setting the .spec field of the Output and ClusterOutput objects instead of harcoding them to Loki or OpenSearch. - added new type to the schema - added new customOutputs field to the spec.distribution.modules.logging field with options to configure the outputs - added new constraints to the schema - updated the schema docs - updated kustomize base for logging - added migrations for the new logging type
- add ingress manifests for Hubble UI behind pomerium when auth is enabled - update networking schema to allow overriding defaults - update schemas documentation - update go-models Note: this does not update EKS schema because cilium is not an option there.
this patch makes the containerd configuration template more flexible to support configuring registry mirrors without needing to set also the authentication, auth details where previously always required otherwise the templating would fail.
…monitoring type This is a set of changes that allow the monitoring stack to be configured to send metrics to a remote Prometheus receiver, both with our current Prometheus monitoring type and with a new PrometheusAgent type that deploys a more minimal Prometheus intallation only for scraping and sending metrics. - Add `remoteWrite` section to prometheus' configuration in the scheam, so Prometheus can be set up to send metrics to a remote receiver. - Add prometheusAgent as monitoring type, as an alternative to prometheus+remoteWrite, allowing to have a "minimal" monitoring stack capable of sending metrics to a remote Prometheus receiver. Notice that this mode does not allow for querying the local Prometheus instance (so no local Grafana dashboards) or having local alerting set up. - Add migrations for switching between Prometheus and Prometheus Agent, and to and from `none`. - Update documentation with the new features
- update schema docs with md-gen - update go models
enable metrics scraping from the haproxy loadbalancers and deploy the dashboards and alerts for haproxy from the monitoring module.
Add new schema fields to configure Pomerium
feat(monitoring): add remoteWrite to Prometheus and Prometheus Agent mode
feature(networking): add internal Hubble ingress
feat: new logging type customOutputs
…rors feature(onpremises): support containerd mirrors
feature(dr): add selectors and tolerations to minio and velero on-prem
feature(dr): modify velero cron
feature(onprem): enable haproxy monitoring
…-oidc feat: additional parameters for oidc settings
…ng kubernetes_kubeconfig_path and paths.kubectl anymore. Also, removed the check if we are using docker or containerd, since docker has been removed in the distro supported versions + add rsync installation since it was missing on the default installation
feat: add playbook tpl for cluster certificates renewal
Docs/v1.29.2 and lower versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.