For each API tier defined by Red Hat, we provide a mapping table for specific API groups where the upstream communities are committed to maintain forward compatibility. Any API group that does not specify an explicit compatibility level and is not specifically discussed below is assigned API tier 3 by default except for v1alpha1
APIs which are assigned tier 4 by default.
API groups that end with the suffix *.k8s.io
or have the form version.<name>
with no suffix are governed by the Kubernetes deprecation policy and follow a general mapping between API version exposed and corresponding support tier unless otherwise specified.
API version example | API tier |
---|---|
|
Tier 1 |
|
Tier 2 |
|
Tier 4 |
API groups that end with the suffix *.openshift.io
are governed by the {product-title} deprecation policy and follow a general mapping between API version exposed and corresponding compatibility level unless otherwise specified.
API version example | API tier |
---|---|
|
Tier 1 |
|
Tier 1, some tier 1 deprecated |
|
Tier 1, some tier 1 deprecated |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 |
|
Tier 1 except for |
|
Tier 1 |
|
Tier 2 |
API groups that end with the suffix monitoring.coreos.com
have the following mapping:
API version example | API tier |
---|---|
|
Tier 1 |