---
# System prepended metadata

title: Untitled
tags: [advantech, report]

---

## Review Operator : https://github.com/Ultimaker/k8s-mongo-operator
Date: 1/7/2019 - 2/7/2019
Reviewer: Fransiscus Bimo


###### tags: `advantech` `report` 
-----
### Findings:
- Lack of documentation

- conventional way to deploy instance
    still use command as below: 
```
kubectl apply -f object.yaml
```


- Failed to perform delete through Mongo object file
![](https://i.imgur.com/fn9dcVK.png)

- Failed to perform delete through API
![](https://i.imgur.com/Bp1BMaO.png)

- NO parameter option for serviceType(LoadBalancer,NodePort) in the object.yaml 
```json=
apiVersion: "operators.ultimaker.com/v1"
kind: Mongo
metadata:
  name: mongo-cluster2-ef
spec:
  mongodb:
    replicas: 2
  backups:
    cron: "0 * * * *" # hourly
    gcs:
      bucket: "ultimaker-mongo-backups"
      serviceAccount:
        secretKeyRef:
          name: "storage-service-account"
          key: json
```
- No log confirmation when create successful
- No deployment resources when deploy
![](https://i.imgur.com/gmPMqR2.png)

- If Mongo object removed, re-deployment using yaml only shows object is created but there are no pods created
![](https://i.imgur.com/odWw7fc.png)
![](https://i.imgur.com/ZOtHeX7.png)
- python based, big size container
 ![](https://i.imgur.com/4mNtbQ4.png)

- Long time to deploy multiple object
![](https://i.imgur.com/Egd4uZI.png)


### Conclusion
Based on findings that i have done, this version of MongoDB operator is **NOT** recommended for production deployment

