-
Notifications
You must be signed in to change notification settings - Fork 38
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
[KO-290] Allow enabling security in the existing deployed cluster #273
Conversation
api/v1/aerospikecluster_types.go
Outdated
@@ -871,6 +871,9 @@ type AerospikePodStatus struct { //nolint:govet // for readability | |||
|
|||
// PodSpecHash is ripemd160 hash of PodSpec used by this pod | |||
PodSpecHash string `json:"podSpecHash"` | |||
|
|||
// SecurityEnabled is true if security is enabled in the pod | |||
SecurityEnabled bool `json:"securityEnabled"` |
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 think a better name would be IsSecurityEnabled
|
||
enabled, newErr = asdbv1.IsSecurityEnabled( | ||
incomingVersion, incomingVersionErr := asdbv1.GetImageVersion(desiredState.Image) |
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.
Shouldn't we check for the enable security from spec by default? If it is not enabled then look into the status.
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.
The idea here was to send Aerospike credentials if security is enabled in either the spec or status. Following that, we check for AerospikeAccessControl
in the status
to determine whether to use user-provided credentials or the default admin credentials.
No description provided.