Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AAP-34599: updates procedure for signing EEs #2821

Merged
merged 6 commits into from
Jan 31, 2025
Merged

AAP-34599: updates procedure for signing EEs #2821

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
97a35b0
updates procedure for signing EEs
hherbly Jan 24, 2025
1cc205b
linking new content in containerized install guide
hherbly Jan 30, 2025
902efa9
fixed link
hherbly Jan 30, 2025
b504973
updates proc for signing an EE
hherbly Jan 31, 2025
628ae93
removes one errant bracket
hherbly Jan 31, 2025
e0d6f3e
edit based on peer review feedback
hherbly Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 15 additions & 9 deletions downstream/modules/hub/proc-adding-an-execution-environment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,26 +1,32 @@

[id="adding-an-execution-environment"]

= Adding an {ExecEnvShort}
= Adding and signing an {ExecEnvShort}
{ExecEnvNameStart} are container images that make it possible to incorporate system-level dependencies and collection-based content. Each {ExecEnvShort} allows you to have a customized image to run jobs, and each of them contain only what you need when running the job.

.Procedure
. From the navigation panel, select {MenuACExecEnvironments}.

. Click btn:[Create execution environment].
. Click btn:[Create execution environment] and enter the relevant information in the fields that appear.

. Enter the name of the {ExecEnvShort}.
.. The *Name* field displays the name of the {ExecEnvShort} on your local registry.

. Enter the upstream name.
.. The *Upstream name* field is the name of the image on the remote server.

. Under *Registry*, select the name of the registry from the drop-down menu.
.. Under *Registry*, select the name of the registry from the drop-down menu.

. Enter tags in the *Add tag(s) to include* field.
.. Optional: Enter tags in the *Add tag(s) to include* field.
If the field is blank, all the tags are passed.
You must specify which repository-specific tags to pass.

. Optional: Enter tags to exclude in *Add tag(s) to exclude*.
.. Optional: Enter tags to exclude in the *Add tag(s) to exclude* field.

. Click btn:[Create {ExecEnvName}].
. Click btn:[Create {ExecEnvShort}]. You should see your new {ExecEnvNameSing} in the list that appears.

. Synchronize the image.
. Sync and sign your new {ExecEnvNameSing}.

.. Click the btn:[More Actions] icon *{MoreActionsIcon}* and select *Sync execution environment*.

.. Click the btn:[More Actions] icon *{MoreActionsIcon}* and select *Sign execution environment*.

. Click on your new {ExecEnvNameSing}. On the Details page, find the *Signed* label to determine that your {ExecEnvNameSing} has been signed.
3 changes: 1 addition & 2 deletions downstream/modules/hub/proc-deploying-your-system-for-container-signing.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,8 @@

= Deploying your system for container signing

{HubNameStart} implements image signing to offer better security for the {ExecEnvShort} container images.

To deploy your system so that it is ready for container signing, create a signing script.
To deploy your system so that it is ready for container signing, first ensure that you have link:{URLContainerizedInstall}/aap-containerized-installation#enabling-automation-hub-collection-and-container-signing_aap-containerized-installation[enabled automation content collection and container signing]. Then you can create a signing script, or xref:proc-adding-an-execution-environment.adoc[add and sign an {ExecEnvShort}] manually.

[NOTE]
====
Expand Down