edupo
Cadet
Cadet
  • 392 Views

Building and uploading execution environments

Jump to solution

We are adapting our legacy container build pipeline based on docker and kaniko. It is currently used by our organization in pretty much every container we build.

When start adapting that pipeline to build an EE we found that the Private Automation Hub was throwing 500 errors during upload from Kaniko... After opening a support case (03481235) we were told (ofc) that those tools are not supported and we were pointed to very sallow tutorials on how to build EE...

We have decided to use Nexus instead of PAH to host EE since PAH seems not mature enough to assume established tools.

How do you plan to support migration if customer processes are established? Are you going to enforce only your tools where legacy solutions have been working for years? Do you also advise about all these hidden costs for a migration?

Thank you

Labels (1)
1 Solution

Accepted Solutions
  • 350 Views

Hi Edupo,

Although Private Automation Hub is the recommended way of hosting Ansible content like collection and EEs for your organization, the EEs are essentially container images and any container registry can host execution environments. If you want to use any other registry like Nexus in your case, it should not be an issue but there are certain features that specifically available in Private Automation Hub and you won't get advantage of those features if you don't host execution environments there.

For instance, One of those features is the ability to sign execution environments in automation hub to ensure secure supply chain. 

But any registry to host execution environments should be alright if you already have established tools in your organizations.

View solution in original post

1 Reply
  • 351 Views

Hi Edupo,

Although Private Automation Hub is the recommended way of hosting Ansible content like collection and EEs for your organization, the EEs are essentially container images and any container registry can host execution environments. If you want to use any other registry like Nexus in your case, it should not be an issue but there are certain features that specifically available in Private Automation Hub and you won't get advantage of those features if you don't host execution environments there.

For instance, One of those features is the ability to sign execution environments in automation hub to ensure secure supply chain. 

But any registry to host execution environments should be alright if you already have established tools in your organizations.

Join the discussion
You must log in to join this conversation.