-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #26 from rthallisey/simplify-api
Simplify the Cincinnati Operator API
- Loading branch information
Showing
8 changed files
with
80 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
# External Registry CA Injection | ||
|
||
If you are using a secure external container registry to hold mirrored OpenShift | ||
release images, Cincinnati will need access to this registry in order to build | ||
an upgrade graph. Here's how you can inject your CA Cert into the Cincinnati | ||
pod. | ||
|
||
OpenShift has an external registry API, located at `image.config.openshift.io`, | ||
that we'll use to store the external registry CA Cert. You can read more about | ||
this API in the [OpenShift documentation](https://docs.openshift.com/container-platform/4.3/registry/configuring-registry-operator.html#images-configuration-cas_configuring-registry-operator). | ||
|
||
Create a ConfigMap in the `openshift-config` namespace. Fill in your CA Cert | ||
under the key `cincinnati-registry`, because it's how Cincinnati locates your Cert: | ||
```yaml | ||
apiVersion: v1 | ||
kind: ConfigMap | ||
metadata: | ||
name: trusted-ca | ||
data: | ||
cincinnati-registry: | | ||
-----BEGIN CERTIFICATE----- | ||
... | ||
-----END CERTIFICATE----- | ||
``` | ||
Edit the `cluster` resource from the `image.config.openshift.io` API and set | ||
the `additionalTrustedCA` field to the name of the ConfigMap you just created | ||
above. | ||
```bash | ||
$ oc edit image.config.openshift.io cluster | ||
spec: | ||
additionalTrustedCA: | ||
name: trusted-ca | ||
``` | ||
|
||
The Cincinnati Operator will watch the `image.config.openshift.io` API and the | ||
ConfigMap you created in the `openshift-config` namespace for changes, then | ||
restart the deployment if the Cert has changed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters