What would you like to be added:

Enable Dynamic Persistent volume Provisioning for ceph rbd provisioner through adding "allowVolumeExpansion" parameter.

Why is this needed:

Dynamic Persistent volume Provisioning is necessary and ceph rbd support this.

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

I recently installed the microk8s snap on a vanilla LXD container. At the time I hadn't come across https://microk8s.io/docs/lxd and it took a little while before I noticed that some components hadn't started up properly and I found my way to that doc.

Having found the documentation, it's excellent, thank you - following the instructions there left me with a very happy microk8s instance. From a

When following:
https://www.telepresence.io/tutorials/docker

We come to the part where we do a swap-deployment:

$ telepresence --swap-deployment hello-world --docker-run --rm -it -v $(pwd):/usr/src/app hello-dev
T: Volumes are rooted at $TELEPRESENCE_ROOT. See https://telepresence.io/howto/volumes.html for details.
T: Starting network proxy to cluster by swapping out Deployment hell

Add a test sending (e.g. config map) patches through the same API using:

• JSON patch
• Strategic merge patch

make sure the API client is able to set the content type properly according to the request body, and the patches are applied successfully.

ref: https://github.com/ku

Use case

Polyaxon tracking can be used to automatically log all information generated by Ludwig.

We should probably think about adding support for Polyaxon's tracking module in Ludwig contrib.

Currently, apart from using some of the existing properties on the nodes, there is no way to exclude the node that runs the Seal from attack.

It would be really nice to add that to be handled automatically.

Check to confirm CloudTrail is configured for multi-region.

CloudFormation - IsMultiRegionTrail: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudtrail-trail.html

Background

As discussed in #223 comments (zalando-incubator/kopf#223 (comment) and below), there is one type of handlers is missing: when an operator restarts, it should process all the objects that existed before, but were neither updated, nor deleted.

Originally, this was a technical solution for @kopf.on.resume() handlers in #96. But then it was

There are in other helm chart many nice example documentation in comments of values.yaml, we don't have much of that. See for example GitLabs' Helm charts for GitLab itself or GitLab runners and note how they use ## and # differently. Also read ab