-
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
E2E for cluster connection via Ingress #1076
Conversation
164b07c
to
c7f8960
Compare
2a3854a
to
7cf670a
Compare
base on the examples from: scylladb/scylla-operator#1076
base on the examples from: scylladb/scylla-operator#1076
base on the examples from: scylladb/scylla-operator#1076
base on the examples from: scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
base on the examples from: scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
To be able to support creation of the 'ingress' objects we should install 'ingress controller' in our K8S clusters. So, add this possibility using configuration taken from [1]. To enable it's installation and appropriate configuration of Scylla clusters just set 'k8s_enable_tls: true' config option. [1] scylladb/scylla-operator#1076
75f6fcb
to
37800b9
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
37800b9
to
249fb41
Compare
overriding stale job |
@zimnx: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. 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. |
249fb41
to
d95e17c
Compare
@zimnx: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
d95e17c
to
5f9dc35
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.
one open conversation, the rest lgtm - thanks for the updates
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
thanks
E2E test validating whether clients can connect to ScyllaDB cluster via CQL Connection Config using Ingresses.
Test binary is extended with three parameters:
--ingress-controller-address
- address allowing to connect to deployed proxy.--ingress-controller-ingress-class-name
- must match the deployed ingress controller class.--ingress-controller-custom-annotations
- haproxy requires special annotation to enable passthrough mode, it can be configured via this parameter.Fixes #1015