internet/awx-operator
3
0
Fork 0
mirror of https://github.com/ansible/awx-operator.git synced 2026-05-08 06:12:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Do not check for default ee-pull-cred secret

Browse Source 
* fix nested var ref for awx_spec.spec
This commit is contained in:
Christian M. Adams
2021-07-01 10:26:50 -04:00
parent c0ff27a8e6
commit cf2cd14154
3 changed files with 7 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -577,7 +577,7 @@ Example configuration for ConfigMap
#### Default execution environments from private registries
In order to register default execution environments from private registries, the Custom Resource needs to know about the pull credentials. Those credentials should be stored as a secret and either specified as `ee_pull_credentials_secret` at the CR spec level, or simply be present on the namespace under the name `<resourcename>-ee-pull-credentials` . Instance initialization will register a `Container registry` type credential on the deployed instance and assign it to the registered default execution environments.
In order to register default execution environments from private registries, the Custom Resource needs to know about the pull credentials. Those credentials should be stored as a secret and specified as `ee_pull_credentials_secret` at the CR spec level. Instance initialization will register a `Container registry` type credential on the deployed instance and assign it to the registered default execution environments.
The secret should be formated as follows:
@@ -586,7 +586,7 @@ The secret should be formated as follows:
apiVersion: v1
kind: Secret
metadata:
name: <resourcename>-ee-pull-credentials
name: my-ee-pull-credentials
namespace: <target namespace>
stringData:
url: <registry url. i.e. quay.io>
@@ -596,7 +596,7 @@ stringData:
type: Opaque
```
##### Control plane ee from private registry
##### Control plane EE from private registry
The images listed in "ee_images" will be added as globally available Execution Environments. The "control_plane_ee_image" will be used to run project updates. In order to use a private image for any of these you'll need to use `image_pull_secret` to provide a k8s pull secret to access it. Currently the same secret is used for any of these images supplied at install time.
You can create `image_pull_secret`