Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow posix path for communal storage #308

Merged
merged 2 commits into from
Dec 30, 2022
Merged

Conversation

spilchen
Copy link
Collaborator

This relaxes some checks in the webhook so that we can use a POSIX path for communal storage. This should be used only for development purposes. A supported communal path (e.g. S3, HDFS, etc.) should still be used if deploying a production environment. This is to aid in development as it will allow for faster deployments as we don’t need a communal storage service running such as minio. Instead, if you are running on a single host you can use a host path to share communal storage across pods.

Also, I am adding a back door to allow the operator to create and manage an enterprise database. You can get into this mode if you set the shard count in the CR to zero. There is a webhook rule that prevents this, so you will need to disable the webhook to run it this way. This is being added for internal dev testing and is by no way an officially supported use of the operator.

@spilchen spilchen self-assigned this Dec 30, 2022
@spilchen spilchen merged commit 95330f9 into vertica:main Dec 30, 2022
@spilchen spilchen deleted the hostpath branch December 30, 2022 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant