You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the past, with pulp_installer, we had playbooks to do a “complete” installation of Pulp and its components.
We should update our CR samples with more combinations of installations, like:
install Pulp with signing metadata (with {file,object} storage and bellow combinations)
some variations of ingress types (ingress, route, node_port)
combinations of external DB and/or cache
update the current samples with the deprecated pulp_settings field to use custom_pulp_settings
etc.
this would be helpful to avoid having to first install Pulp and then having to modify/tweak the CR to enable the feature A or change the unwanted behavior B.
Additional context
Update our docs explaining the usage of these samples.
The text was updated successfully, but these errors were encountered:
In the past, with
pulp_installer
, we had playbooks to do a “complete” installation of Pulp and its components.We should update our CR samples with more combinations of installations, like:
pulp_settings
field to usecustom_pulp_settings
this would be helpful to avoid having to first install Pulp and then having to modify/tweak the CR to enable the feature A or change the unwanted behavior B.
Additional context
Update our docs explaining the usage of these samples.
The text was updated successfully, but these errors were encountered: