When defining a custom resource object starting in the yaml form view,  results in some of the default values  not being populated[1].

However, should you switch to the form view only to return to the yaml view, you will notice the Pachyderm object would have more fields defined even prior to any user input[2]. For example, see the field, `worker.serviceAccountName`.

The affected default values are defined using kubebuilder markers in the pachyderm_types.go file. See [block](https://github.com/OchiengEd/pachyderm-operator/blob/30450d69a4af38bdc0ef312d30860d43cf0a6fcf/api/v1beta1/pachyderm_types.go#L71-L75) provided

The expectation is the operator would behave the same when created using the different views.

[1]
kind: Pachyderm
apiVersion: aiml.pachyderm.com/v1beta1
metadata:
name: pachyderm-sample
namespace: bug-report
spec:
console:
disable: true
pachd:
metrics:
disable: false
storage:
amazon:
credentialSecretName: pachyderm-aws-secret
backend: AMAZON
version: v2.1.6

[2]
apiVersion: aiml.pachyderm.com/v1beta1
kind: Pachyderm
metadata:
name: pachyderm-sample
namespace: bug-report
spec:
console:
disable: true
etcd:
storageSize: 10Gi
pachd:
logLevel: info
metrics:
disable: false
ppsWorkerGRPCPort: 1080
postgresql:
database: pachyderm
host: postgres
port: 5432
ssl: disable
user: pachyderm
storage:
amazon:
credentialSecretName: pachyderm-aws-secret
putFileConcurrencyLimit: 100
uploadFileConcurrencyLimit: 100
backend: AMAZON
worker:
serviceAccountName: pachyderm-worker
version: v2.1.6

This behavior was first reported by the RHODS team in the Jira issue attached here in at https://issues.redhat.com/browse/RHODS-2651