Project

Profile

Help

Story #5137

closed

Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io

As a pulp-operator user, I can configure & expand the storage volume size

Added by mdepaulo@redhat.com over 4 years ago. Updated over 2 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
Operator - Moved to Github Issues
Sprint/Milestone:
-
Start date:
Due date:
% Done:

80%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

h1. !! Ticket moved to GitHub: "pulp/pulp-operator/258":https://github.com/pulp/pulp-operator/issues/258


pulp-operator currently uses static sized Persistent Volume Claims for both the PostgreSQL database and for /var/lib/pulp .

This is unacceptable because by adding/syncing more content, users can exceed the capacity. Also, the current values may be too large.

Actions #1

Updated by mdepaulo@redhat.com over 4 years ago

Research suggests that the best way to do this is a ConfigMap that the operator references. Other operators do this, such as mongodb and another.

Actions #2

Updated by mdepaulo@redhat.com over 4 years ago

  • % Done changed from 0 to 50

As part of implementing this task on the k3s-travis branch, I started on this.
https://pulp.plan.io/issues/5061

We currently have configurable storage via a ConfigMap. But I do not know if it can expanded afterwards.

Actions #3

Updated by mdepaulo@redhat.com over 4 years ago

The storage can be expanded by uploading a new version of the ConfigMap. It takes seconds for the change to start being applied by the pulp-operator (ansible operator) pod.

However, the StorageClass / provisioner must support it.

The minikube-hostpath provisioner does not, even if you modify its storage class ("Standard".) (This may be due to the lack of the Online File System Expansion feature "ExpandInUsePersistentVolumes").

However, other provisioners do, such as AWS-EBS, GCE-PD, Azure Disk, Azure File, Glusterfs, Cinder, Portworx, and Ceph RBD.
https://kubernetes.io/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/

Added by Mike DePaulo over 4 years ago

Revision 7d222c37 | View on GitHub

Use pulp-file-storage settings from a ConfigMap

Add different ConfigMaps for known use cases like Travis

Partially implements: ref #5137 https://pulp.plan.io/issues/5137

Actions #4

Updated by mdepaulo@redhat.com over 4 years ago

I have discovered that the better way to solve this is to use our operator's custom resource.

This is what we already do for the pulp image tag. And it is what the ansible operator framework is designed around.

I plan to rework the existing configmap into the custom resource.

Actions #5

Updated by mdepaulo@redhat.com over 4 years ago

  • % Done changed from 50 to 80

This is now being done for Pulp itself via a custom resource.

Still needs to be done for postgres.

Actions #6

Updated by fao89 about 4 years ago

  • Tags CI/CD added
Actions #7

Updated by fao89 over 3 years ago

  • Category set to Operator - Moved to Github Issues
Actions #8

Updated by mdepaulo@redhat.com about 3 years ago

  • Subject changed from pulp-operator needs configurable and expandable storage size to As a pulp-operator user, I can configure & expand the storage volume size
Actions #9

Updated by mdepaulo@redhat.com about 3 years ago

  • Tags deleted (CI/CD)
Actions #10

Updated by mdepaulo@redhat.com about 3 years ago

  • Assignee deleted (mdepaulo@redhat.com)
Actions #11

Updated by fao89 over 2 years ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF