Skip to content

Entitled builds and OpenShift 4

With entitled builds, we have to cover two main topics:

  1. How to get the entitlement and refresh the entitlement

  2. How to provide/attach the entitlement to the build.

Let’s elaborate on the first one: How to get the entitlement.

Technically, the entitlement is a certificate to get access to specific Red Hat Enterprise Linux content and have to refresh regularly. Red Hat introduce Simple Content Access to simplify the access, for example for container builds.

With openssl or rct command you can get some information from your entitlement:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
$ rct stat-cert /etc/pki/entitlement/entitlement.pem
Type: Entitlement Certificate
Version: 3.4
DER size: 1610b
Subject Key ID size: 20b
Content sets: 5835
$ openssl x509 -in /etc/pki/entitlement/entitlement.pem -noout -issuer
issuer=C = US, ST = North Carolina, O = "Red Hat, Inc.", OU = Red Hat Network, CN = Red Hat Candlepin Authority, emailAddress = ca-support@redhat.com
$ rct cat-cert  /etc/pki/entitlement/entitlement.pem  | head -n15

+-------------------------------------------+
    Entitlement Certificate
+-------------------------------------------+

Certificate:
    Path: /etc/pki/entitlement/entitlement.pem
    Version: 3.4
    Serial: <Cert Serial>
    Start Date: 2022-07-10 03:19:11+00:00
    End Date: 2023-07-10 03:19:11+00:00
    Pool ID: Not Available

Subject:
    CN: xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx

How to get the entitlement certificate? If simple content access is enabled at your organisation/redhat account, the insights Operatos automatically provide and refresh and entitlement to your OpenShift 4 Cluster.

You can enable and check the Simple content access at https://access.redhat.com/management, it should look like this:

At your OpenShift 4 Cluster you can take a look your entitlement via: 

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
$ oc get secrets etc-pki-entitlement -n openshift-config-managed  -o jsonpath="{.data.entitlement\.pem}" | base64 -d > entitlement.pem

$ rct cat-cert entitlement.pem | head -n15

+-------------------------------------------+
    Entitlement Certificate
+-------------------------------------------+

Certificate:
    Path: entitlement.pem
    Version: 3.4
    Serial: <Cert Serial>
    Start Date: 2022-07-10 05:06:45+00:00
    End Date: 2023-07-10 05:06:45+00:00
    Pool ID: Not Available

Subject:
    CN: xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx
$

Relevant documentation part: Importing simple content access certificates with Insights Operator

Another option to get an entitlement from your Red Hat Satellite installation in your environment. Or copy the entitlement from a subscribed Red Hat Enterprise Linux - this is not recommended, and I assume this is against Red Hat Terms and conditions.

Let’s elaborate on the second one: How to provide/attach the entitlement to the build.

There are three options to attach the entitlement to a build – build pod at the end:

  1. Simple attaches a secret with the entitlement to the build. Documentation: Adding subscription entitlements as a build secret

  2. Leverage the Shared Resource CSI Driver Operator (Technology Preview) to share the etc-pki-entitlement secrets from openshift-config-managed namespace provided by the Insights Operator.

  3. Rollout entitlement cluster-wide via MachineConfigOperator. Not recommend because it changes every single build behavior in the OpenShift Cluster, additional you have to update the MachineConfig to the new entitlement regularly.

Let’s take a more in-depth look at the Shared Resource CSI solution:

First enable the Shared Resource CSI Driver Operator via FeatureGates:

Then wait for the MachineConfigPool is updated and shared resources objects are available:

1
2
3
$  oc api-resources | grep  sharedresource
Sharedconfigmaps  sharedresource.openshift.io/v1alpha1 false SharedConfigMap
Sharedsecrets     sharedresource.openshift.io/v1alpha1 false SharedSecret

Create an sharedsecrets object (cluster scoped):

1
oc apply -f https://examples.openshift.pub/build/entitled/etc-pki-entitlement.SharedSecret.yaml

1
2
3
4
5
6
7
8
apiVersion: sharedresource.openshift.io/v1alpha1
kind: SharedSecret
metadata:
  name: etc-pki-entitlement
spec:
  secretRef:
    name: etc-pki-entitlement
    namespace: openshift-config-managed

Create a project/namespace

1
oc create project entitled-build-demo

Grant access to SharedSecret etc-pki-entitlement

1
2
oc apply -f https://examples.openshift.pub/build/entitled/etc-pki-entitlement.Role.yaml
oc apply -f https://examples.openshift.pub/build/entitled/etc-pki-entitlement.RoleBinding.yaml

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: etc-pki-entitlement
rules:
- apiGroups:
  - sharedresource.openshift.io
  resourceNames:
  - etc-pki-entitlement
  resources:
  - sharedsecrets
  verbs:
  - use
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: etc-pki-entitlement
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: etc-pki-entitlement
subjects:
- kind: ServiceAccount
  name: builder
  namespace: entitled-build-demo

Create ImageStream and BuildConfig with access to entitlement

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
---
apiVersion: image.openshift.io/v1
kind: ImageStream
metadata:
  name: entitled
spec: {}
---
apiVersion: build.openshift.io/v1
kind: BuildConfig
metadata:
  name: entitled
spec:
  nodeSelector: null
  output:
    to:
      kind: ImageStreamTag
      name: entitled:latest
  runPolicy: Serial
  source:
    dockerfile: |
      FROM registry.redhat.io/ubi8/ubi:latest
      RUN rm /etc/rhsm-host
      RUN dnf search kernel-devel --showduplicates && \
              dnf install -y kernel-devel
    type: Dockerfile
  strategy:
    dockerStrategy:
      volumes:
      - mounts:
        - destinationPath: /etc/pki/entitlement
        name: etc-pki-entitlement
        source:
          csi:
            driver: csi.sharedresource.openshift.io
            readOnly: true
            volumeAttributes:
              sharedSecret: etc-pki-entitlement
          type: CSI
    type: Docker

1
2
oc apply -f https://examples.openshift.pub/build/entitled/etc-pki-entitlement.ImageStream.yaml
oc apply -f https://examples.openshift.pub/build/entitled/etc-pki-entitlement.BuildConfig.yaml

Additional Resources

2022-12-08 2020-05-12 Contributors: Robert Bohne