-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add enhancement proposal to support Alternator API #1406
Add enhancement proposal to support Alternator API #1406
Conversation
|
||
- Exposing Alternator on every node individually and relying on client side load balancing | ||
- Supporting host networking tweaks | ||
- Disabling CQL when Alternator is enabled |
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.
@tzach I recall you wanted the reverse but given CQL is needed for scaling procedures and AuthZ I don't see an easy way out
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.
solid, a couple of nits
/approve
Also please remember to change the path from |
The proposal is also missing the |
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.
first pass
I've noticed ScyllaDB sets up alternator HTTPS in tests on |
d6f7df9
to
ac2ef3b
Compare
I've found the section present in exactly 50% of the existing proposals and I haven't made up my mind on that yet. Maybe it's more useful to add from a second pass on but added it here. |
Typo in the path - should be |
ac2ef3b
to
b9585c3
Compare
renamed, thx |
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: rzetelskik, 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 |
|
||
## Summary | ||
|
||
This proposal aims to introduce proper support for enabling Alternator for ScyllaClusters |
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.
This proposal aims to introduce proper support for enabling Alternator for ScyllaClusters | |
This proposal aims to introduce proper support for enabling Alternator for Scylla Clusters |
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.
we are intentionally putting those together as it's the exact CRD name
### Certificates | ||
|
||
Given we aim to always enable HTTPS we need to provision default serving certificate. Operator will create signer Secret `<sc-name>-local-alternator-serving-ca`, save the CA bundle into ConfigMap `<sc-name>-local-alternator-serving-ca` and create serving Secret `<sc-name>-local-alternator-serving-certs`. | ||
Serving certs will be valid for 30 days and rotated from 20 day mark. |
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.
This looks unusual low validity and quick rotation. I'm aware of 90 days or 1 year as more regular defaults.
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.
This is in line with the other certificates we create.
I've seen 1y to be used only with manual renewals, I think Let's Encrypt prod CA is on 90d but mostly because some of the clients are not automated and this was a compromise between that. Security wise the lower the better. 1 month still gives enough time to deal with issues while giving a good security policy.
I'm missing the proposed YAML changes (which is the 'interface' a user would use to enable it) |
|
||
### API changes for ScyllaClusters.scylla.scylladb.com/v1 | ||
|
||
The following API changes show how we'd approximately extend `scyllaclusters.scylla.scylladb.com/v1.spec.alternator` specification. Only new fields are shown for existing structs. |
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.
I'm not sure I'm seeing the port definition (8043 by default, I assume) ?
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.
yep, we chose 8043
- described in https://github.com/scylladb/scylla-operator/pull/1406/files#diff-e7c253eebc3e6c9a4c7923ddf75c5c939cfe058d9cf01f085803b4974c2f378eR38
yaml file is an instance of a schema, one of many possible instantiations. The various options and the schema is described with the Golang structs and special comments. The name of the yaml field is defined withing the API, say
means there will be a field named so a simple example instance using the schema from spec:
alternator:
insecureEnableHTTP: false
servingCertificate:
type: OperatorManaged (for illustration, some of them can be defaulted) |
@mykaul Thanks for your feedback, I hope I've resolved all your questions but I also know you are out and we need to branch so I'll unhold this. I am happy to address anything you have when you get back as a follow up, if needed. /hold cancel |
/retest |
/override ci/prow/e2e-gke-parallel |
@tnozicka: Overrode contexts on behalf of tnozicka: ci/prow/e2e-gke-parallel, ci/prow/e2e-gke-serial In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description of your changes:
This PRs add a proposal to fully enable Alternator API in a secured way.
Which issue is resolved by this Pull Request:
Resolves #1405
/cc @zimnx @rzetelskik @mykaul @tzach