Enable Scylla encryption (if disabled) for Manager SCT tests

[mikliapko]

Scope:

1. Check if current SCT tests for Manager run with enabled Scylla encryption.
2. If not, make it enabled by default.

[mikliapko]

Currently, for Manager tests we configure scylla.yaml in a next way:

• enabled client encryption

client_encryption_options:
  certificate: /etc/scylla/ssl_conf/client-facing.crt
  enabled: true
  keyfile: /etc/scylla/ssl_conf/client-facing.key
  truststore: /etc/scylla/ssl_conf/ca.pem

• enabled EaR

kms_hosts:
  auto:
    aws_region: us-east-1
    aws_use_ec2_credentials: true
    master_key: alias/testid-68565fdc-a174-463f-aba0-1b77ad4d56f4
system_info_encryption:
  enabled: true
  key_provider: KmsKeyProviderFactory
  kms_host: auto
user_info_encryption:
  enabled: true
  key_provider: KmsKeyProviderFactory
  kms_host: auto

It looks like we are missing server encryption only. Can it be important for Manager to have it enabled as well?
@karol-kokoszka @Michal-Leszczynski @VAveryanov8

[mikliapko]

As per the issue #4079 and the reason we were not able to catch it in SCT, the configuration is missing native_transport_port_ssl defined. I believe it was the reason Manager was failing to decide on the port to use?
@VAveryanov8

[Michal-Leszczynski]

It looks like we are missing server encryption only. Can it be important for Manager to have it enabled as well?

@mikliapko the encryption you linked refers to encryption between nodes, so it shouldn't impact SM at all.
On the other hand, if it's really easy to enable it, some SM tests should run with it, just to make sure that it's ok.
But if it's difficult, then I would say that's not worth the effort.

[mikliapko]

@mikliapko the encryption you linked refers to encryption between nodes, so it shouldn't impact SM at all. On the other hand, if it's really easy to enable it, some SM tests should run with it, just to make sure that it's ok. But if it's difficult, then I would say that's not worth the effort.

It shouldn't be an issue to enable it for some runs but since we have a lot of work related to 1-to-1 restore, I'll postpone it for now.