Pulp

12/02/2021

• 
  chambridge Pulp

  07:40 PM · Committed changeset

  Fix node affinity handling. Revision b9da2621 (pulp-operator): Merge pull request #291 from chambridge/bugfix-289-handle-snake-case-conversion
• 
  chambridge Pulp

  03:46 PM · Committed changeset

  * Obtain affinity from raw spec data
  * If affinity and node_affinity are present apply to deployments
  Affected by issue: https://github.com/operator-framework/operator-sdk/issues/1770
  Related to: https://github.com/pulp/pulp-operator/i... Revision bb306ad6 (pulp-operator): Fix node affinity handling.

07/26/2021

• 
  chambridge Pulp

  07:27 PM · Closed issue

  Story #9145 (CLOSED - CURRENTRELEASE): Add backup and restore test to pulp-operator ci/cd testing

  
  The pulp-operator currently supports backup and restore via custom resources. The CI/CD pipeline should have a test that validates this continues to function.
  Test steps:
  - Install operator and create a Pulp custom resource
  - Add ...

07/07/2021

• 
  chambridge Pulp

  05:42 PM · Committed changeset

  Use no_log to avoid credential leaks in operator log Revision 2512da20 (pulp-operator): Merge pull request #160 from chambridge/no_log-updates-avoid-cred-leaks
• 
  chambridge Pulp

  03:24 PM · Committed changeset

  * Add no_log on secret creation
  * Add no_log on k8_info for secrets
  * Add no_log on set_fact handling for credentials
  [noissue] Revision 063ba562 (pulp-operator): Use no_log to avoid credential leaks in operator log

07/06/2021

• 
  chambridge Pulp

  09:50 PM · Committed changeset

  Add pulp content settings Revision 37befbc1 (pulp-operator): Merge pull request #166 from chambridge/add_pulp_content_settings
• 
  chambridge Pulp

  09:37 PM · Committed changeset

  * Update settings values with pulp content service and port
  [noissue] Revision ca86adcc (pulp-operator): Add pulp content settings

07/03/2021

• 
  chambridge Pulp

  02:41 AM · Closed issue

  Applied in changeset commit:pulp-operator|4f134106b50795ac3731b3d469e0bdeb5f746996. Issue #8833 (MODIFIED): API Server binds a NodePort (out of the default range) on OpenShift

  When deploying Pulp via Operator on OpenShift we've encountered an issue [1] with API Server `Service` resource.
  Operator is creating a `Service` resource that binds a nodePort `24817` (specified [2])). This node port is outside the d...
• 
  chambridge Pulp

  02:40 AM · Committed changeset

  Use nodeport flow only when defined, otherwise supply svc.cluster.local option Revision 90d966b8 (pulp-operator): Merge pull request #163 from chambridge/use-nodeport-only-when-requested
• 
  chambridge Pulp

  01:47 AM · Committed changeset

  * Don't attempt nodeport settings if not selected
  * Use status.hostIP from downward API to get node where web pod is running https://stackoverflow.com/a/52047845
  * Only set nodeport for web service
  * Allow user to specify nodeport or tak... Revision 4f134106 (pulp-operator): Use nodeport flow only when defined, otherwise supply svc.cluster.local option