-
Notifications
You must be signed in to change notification settings - Fork 162
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
Move aggregated deploy manifests to deploy folder #1532
Move aggregated deploy manifests to deploy folder #1532
Conversation
e648e6c
to
97ae8a8
Compare
We already have these in the repo at Line 483 in bda16e4
and Line 493 in bda16e4
|
good catch, I forgot about those two. I'll move them to the deploy folder (+add the dev variant) and update the docs links |
97ae8a8
to
62cd444
Compare
62cd444
to
1803b69
Compare
1803b69
to
ea6cba1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
#1433 |
Description of your changes:
Aggregating all deploy manifests allows users to do
kubectl apply --server-side -f https://github.com/scylladb/scylla-operator/raw/master/deploy/operator.yaml
that complements the localkubectl apply --server-side -f deploy/operator/
Moving the aggregated manifests to deploy folder ensures they can be found and referenced in out install scenarios.
This also add an aggregated version of dev setup for manager.
Resolves #1533