Alternator's user managed serving certificate is not supported

[rzetelskik]

I've noticed that although our API has an option for user managed serving certificate for alternator

scylla-operator/pkg/api/scylla/v1/types_cluster.go

Line 570 in 59f6593

UserManagedOptions *UserManagedTLSCertificateOptions `json:"userManagedOptions,omitempty"`

, the certs are only set up for operator managed type:

scylla-operator/pkg/controller/scylladbdatacenter/sync_certs.go

Line 408 in 59f6593

if sdc.Spec.ScyllaDB.AlternatorOptions != nil &&

scylla-operator/pkg/controller/scylladbdatacenter/resource.go

Line 564 in 59f6593

if sdc.Spec.ScyllaDB.AlternatorOptions != nil {

We should set up certificate plumbing for user managed type, and support mirroring of it in ScyllaDBCluster.

/kind bug

[tnozicka]

We should set up certificate generation for user managed type as well.

User managed kind of means we don't generate the certs but only configure the given one.

[rzetelskik]

but only configure the given one

which we don't, although yes, it manifests in resource creation, not in cert generation

[tnozicka]

which we don't

I guess it works with the same name only today but we should fix plumbing it through

[scylla-operator-bot]

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 30d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out

/lifecycle stale

[rzetelskik]

/triage accepted