v0.1.49

What's Changed

• An error preventing the Venafi Kubernetes Agent deployment on Red Hat OpenShift clusters has been resolved. The error "runAsUser: Invalid value: 1000" is no longer encountered. By @ThatsMrTalbot in #546
• You no longer have to scroll up in the logs to find out why the agent pod has crashed. The last log line before the process exits now shows the reason for giving up. By @james-w in #537
• The Helm chart venafi-kubernetes-agent has been improved:
  • When a proxy for outbound connections to api.venafi.cloud or api.venafi.eu is required, and the proxy uses a certificate issued by a private certificate authority, you can now add the certificate authority to a custom CA bundle that will be trusted by the agent. The Helm chart now supports specifying volumes and volume mounts to streamline this process. By @maelvls in #543
  • The Helm chart has been enhanced to allow users to control the metrics settings. For more information, see the {{ven}} {{k8s}} Agent Helm values reference page. By @wallrj in #544
  • Following best practices, the default CPU limit for the Venafi Kubernetes Agent pod has been removed. This allows for more dynamic resource allocation by Kubernetes. By @wallrj in #539
• The Helm chart for jetstack-secure has also been improved:
  • You can now set volumes and volumeMounts when using the jetstack-agent Helm chart. By @hawksight in #540
  • The jetstack-secure Helm chart version has been bumped to 0.4.0. By @hawksight in #542

New Contributors

• @james-w made their first contribution in #537
• @ThatsMrTalbot made their first contribution in #546

Full Changelog: v0.1.48...v0.1.49