Skip to content
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.

Use the Drupal Operator for Kubernetes instead of custom templates #168

Open
geerlingguy opened this issue Dec 6, 2019 · 3 comments
Open
Labels

Comments

@geerlingguy
Copy link
Owner

It might make things easier to manage...

See: https://github.com/geerlingguy/drupal-operator

Though I would want to be able to use the drupal-for-kubernetes image (and the geerlingguy/drupal image) with this instead of the Docker library Drupal image.

@stale
Copy link

stale bot commented Mar 6, 2020

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Mar 6, 2020
@stale
Copy link

stale bot commented Mar 25, 2020

This issue is no longer marked for closure.

@stale stale bot removed the stale label Mar 25, 2020
@geerlingguy
Copy link
Owner Author

Good thing I didn't work on this until now; the Operator SDK didn't support ARM64 until recently: operator-framework/operator-sdk#2742

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant