Description of problem (please be detailed as possible and provide log
snippets):

Creating an ObjectBucketClaim from the web console triggers an admission webhook warning:
ObjectBucketClaim test violates policy 299 - "unknown field \"spec.ssl\""

Version of all relevant components (if applicable):
OCP 4.16.2
ODF 4.16.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
no. The OBC is still created in the end.

Is there any workaround available to the best of your knowledge?
no

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
yes every time.

Can this issue reproduce from the UI?
yes

If this is a regression, please provide more details to justify this:
I think it might be introduced by https://github.com/red-hat-storage/odf-console/commit/25afe4006361bb9961b0b60335803b8732ac96b9#diff-1984a0679343adf6a8f0410f75ca08f8ae0f4c140708bdd8583768c6f1552193R330 which set the spec.ssl field to false. But there is no spec.ssl field in the model.

Steps to Reproduce:
1. Navigate to Storage > Object Storage > Object Bucket Claims
2. Create an ObjectBucketClaim (any storage class)

Actual results:
Object bucket is created but the UI shows an admission warning.

Expected results:
Object bucket is created without any error or warning.

Additional info: