Blog
Product
Kubernetes
3
minutes

New Feature: Custom Kubernetes Annotations

Kubernetes annotations are key-value pairs attached to Kubernetes objects, providing a flexible way to extend the functionality of your Kubernetes resources without altering their internal specifications. These annotations serve as a tool to store additional metadata to tailor behavior, orchestrate tools, and interact seamlessly with third-party utilities that complement your Kubernetes environment. Today, we're excited to announce that Qovery supports the declaration of Custom Annotations for your Kubernetes clusters 🥳.
September 26, 2025
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

Why Use Kubernetes Annotations?

Using annotations in Kubernetes gives you more control over Kubernetes internal resources like Ingress Controllers, Services, Pods, Deployment, Statefulset, <add your Kubernetes resource type>... and even third-party services. They provide enhanced features and controls without directly modifying the primary resource definitions.

Setting Custom Annotations with Qovery

At Qovery, setting up custom Kubernetes annotations is designed to be straightforward and efficient:

1/ Navigate to your Qovery dashboard and select your application.

2/ In the application settings, scroll down the "General" tab and add your Annotations Group.

Create my annotation group

3/ Select the Annotations Groups you want to attach to your app.

I attach my annotations group to my app

For enhanced management, Qovery introduces Annotations Groups, which allow you to group multiple annotations and apply them across various services, streamlining management and updates.

4/ Finally, save and deploy your changes.

Examples of Kubernetes Annotations

Here are some Kubernetes annotations that you could use:

DataDog Monitoring

This annotation integrates Nginx pods with DataDog's monitoring system to collect detailed metrics.

ad.datadoghq.com/nginx.checks: {"nginx":{"init_config":[],"instances":[{"nginx_status_url":"http://%%host%%/status"}]}}

NGINX Configuration

Adjusts the path of the NGINX ingress controller.

nginx.ingress.kubernetes.io/rewrite-target: /

Hashicorp Vault

Enables HashiCorp Vault to manage secrets for Kubernetes applications securely.

vault.hashicorp.com/role: my-role

Horizontal Pod Autoscaler (HPA)

Autoscale based on custom and external metrics.

autoscaling.kubernetes.io/metrics: "[{'type': 'Resource', 'resource': {'name': 'cpu', 'target': {'type': 'Utilization', 'averageUtilization': 80}}}]"  

Another example: This annotation sets the stabilization window, within a period during which the HPA does not decrease the number of replicas, even if there is no high load. This helps to prevent frequent scale-down operations which could lead to performance degradation during fluctuating loads.

autoscaling.kubernetes.io/scaleDownStabilizationWindowSeconds: 300

Linkerd

Automatically injects Linkerd’s service mesh resources for detailed network and performance monitoring.

linkerd.io/inject: enabled

Prometheus Scraping

Marks pods for scraping by Prometheus directly from Kubernetes.

prometheus.io/scrape: true

Istio Sidecar Injection

Ensures that Istio injects its sidecars for network traffic management within specified pods.

sidecar.istio.io/inject: true

Resource Limits

Defines the resource quota and management tier for the pod or namespace.

quota.management/cluster: gold

Helm Hooks

Specifies custom actions to be taken by Helm post-installation of a chart.

helm.sh/hook: post-install
helm.sh/hook-weight: "-5"
helm.sh/hook-delete-policy: hook-succeeded

Toleration Tags

Allows specific pods to tolerate node taints, facilitating the scheduling of pods on dedicated nodes.

scheduler.alpha.kubernetes.io/tolerations: [{"key":"dedicated","value":"search","effect":"NoSchedule"}]

Those are just a few examples. For more examples, refer to the documentation of services and internal resources deployed on your Kubernetes cluster.

Wrapping Up

Custom Kubernetes annotations on Qovery are now generally available to all users. With the Qovery Annotations Groups feature, Qovery enhances the power of Kubernetes annotations by allowing you to manage them as templates. This feature promotes reusability and ensures consistency across multiple services, simplifying the management and scaling of your Kubernetes applications. Explore this new capability and empower your team to manage Kubernetes more effectively, all within the streamlined developer experience that Qovery promises.

Start using custom Kubernetes annotations with Qovery today and take your infrastructure management to the next level!

Resources: Qovery Kubernetes Annotations documentation

Share on :
Twitter icon
linkedin icon
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
See it in action

Suggested articles

Kubernetes
8
 minutes
Kubernetes management in 2026: mastering Day-2 ops with agentic control

The cluster coming up is the easy part. What catches teams off guard is what happens six months later: certificates expire without a single alert, node pools run at 40% over-provisioned because nobody revisited the initial resource requests, and a manual kubectl patch applied during a 2am incident is now permanent state. Agentic control planes enforce declared state continuously. Monitoring tools just report the problem.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
6
 minutes
Kubernetes observability at scale: how to cut APM costs without losing visibility

The instinct when setting up Kubernetes observability is to instrument everything and send it all to your APM vendor. That works fine at ten nodes. At a hundred, the bill becomes a board-level conversation. The less obvious problem is the fix most teams reach for: aggressive sampling. That is how intermittent failures affecting 1% of requests disappear from your monitoring entirely.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
How to automate environment sleeping and stop paying for idle Kubernetes resources

Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
DevOps
6
 minutes
10 best Kubernetes management tools for enterprise fleets in 2026

The structure, table, tool list, and code blocks are all worth keeping. The main work is fixing AI-isms in the prose, updating the case study to real metrics, correcting the FAQ format, and replacing the CTAs with the proper HTML blocks. The tool descriptions need the "Core strengths / Potential weaknesses" headers made less template-y, and the intro needs a sharper human voice.

Mélanie Dallé
Senior Marketing Manager
DevOps
Kubernetes
Platform Engineering
6
 minutes
10 best Red Hat OpenShift alternatives to reduce licensing costs

For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.

Morgan Perry
Co-founder
AI
Product
3
 minutes
Qovery Skill for AI Agents: Deploy Apps in One Prompt

Use Qovery from Claude Code, OpenCode, Codex, and 20+ AI Coding agents

Romaric Philogène
CEO & Co-founder
Kubernetes
 minutes
Stopping Kubernetes cloud waste: agentic automation for enterprise fleets

Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.

Mélanie Dallé
Senior Marketing Manager
Platform Engineering
Kubernetes
DevOps
10
 minutes
What is Kubernetes? The reality of Day-2 enterprise fleet orchestration

Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.

Morgan Perry
Co-founder

It’s time to change
the way you manage K8s

Turn Kubernetes into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.