Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
7: ARM arch? CMOS?, 9: R&D, leftovers
-
1
Description
When RBAC is enabled, LDAP is also managed, but in a possibly weird way. When the ldap key is defined, then we'll managed as per the manifest, when not, we'll revert to factory settings. This allows on/off, but what it doesn't allow is unmanaged LDAP when RBAC is managed, and thus preventing any possible workaround when RBAC is in use, but LDAP is expected to be manually managed (e.g. the operator doesn't support something).
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Rank | Ranked lower |
| Assignee | Simon Murray [ simon.murray ] | Tommie McAfee [ tommie ] |
| Sprint | 7: ARM arch? CMOS? [ 2023 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Sprint | 7: ARM arch? CMOS? [ 2023 ] | 7: ARM arch? CMOS?, 9: R&D, leftovers [ 2023, 2041 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
Build couchbase-operator-2.3.0-279 contains couchbase-operator commit f59377d with commit message:
K8S-2550: Independent LDAP management
The way to fix this is to have an ldap managed added to CRD.
The reason is because the empty ldap settings can also interpreted as 'remove/reset settings' without implying that user wants to manually manage.