drupal-operator
drupal-operator copied to clipboard
Drupal Operator for Kubernetes, built with Ansible and the Operator SDK.
See: https://sdk.operatorframework.io/docs/building-operators/ansible/migration/
This is a larger issue with Drupal's basic configuration in general... but currently this operator uses the same technique as the PoC, which is a `settings.php` ConfigMap which is mounted...
From the docs: > Ansible Operator also allows you as the developer to supply custom status values with the k8s_status Ansible Module. This allows the developer to update the status...
Currently this operator defaults to the 'official' Docker community drupal image (which is not to be confused with an 'official' Drupal community Docker image—there is none, currently). Instead, maybe we...
If the Drupal deployment image is updated, then we should at minimum run the following Drush commands: 1. `drush updb -y` 2. `drush csim -y` (or `drush cim -y` if...
Inside https://github.com/geerlingguy/drupal-operator/blob/master/roles/drupal/defaults/main.yml, there should be defaults for all the operator spec options, that way if a user doesn't want to supply all of them, they can just rely on the...
Instead of having them inline with the playbook, put them into their own files, just to make things a little more manageable. Either way has it's positives, but I like...
To use different ingresses, in the case also of multiple ingress controllers, it is needed to add some annotations. For example for traefik we need to add: - kubernetes.io/ingress.class: my-ingress-class...
Hi @geerlingguy, Thanks for putting this together! I'm wondering, though, if you're still maintaining this project, or if you think it should be deprecated in favour of something else? After...