<p>In my Kubernetes <code>Service</code>, running on OpenShift, I have an annotation like this:</p>
<pre><code>  annotations:
    service.beta.openshift.io/serving-cert-secret-name: &quot;...&quot;
</code></pre>
<p>which works fine on OpenShift 4.x.</p>
<p>However I also want to support OpenShift 3.11, which requires the similar annotation (note <em>alpha</em>):</p>
<pre><code>service.alpha.openshift.io/serving-cert-secret-name: &quot;...&quot;
</code></pre>
<p>Can I just include <strong>both</strong> annotations in my yaml file in order to support both versions? In other words will OpenShift 4.x ignore the <code>alpha</code> annotation; and will OpenShift 3.11 ignore the <code>beta</code> annotation?</p>

Dave L.
<p>Yes</p>
<p>This is a common pattern for alpha/beta annotation migrations in the Kubernetes ecosystem, the controllers will only be looking for their specific annotation, any the controller doesn't recognise will be ignored.</p>
<p>If a controller is written to be backwards-compatible, they will normally look for the new beta annotation, and only if not finding it respect the alpha one.</p>
