h4. [MSS Operator] As a Developer, I want a Mobile Security Service Operator, such that the Mobile Security Service can be instantiated, used and maintained.
Trello Link: https://trello.com/c/oLKC7jRi/11-mss-operator-as-a-developer-i-want-a-mobile-security-service-operator-such-that-the-mobile-security-service-can-be-instantiated
* An GoLang Operator for the Mobile Security Service (/)
* The MSS Operator should be a cluster level operator (/)
* A Mobile Security Service installation Custom Resource is made available (/)
* The information which will reside in the installation CR should be documented; whats mandatory and whats not and what each piece of info represents.
* When the installation CR is instantiated, the MSS Operator should provision the MSS Service into the namespace where the Operator resides. Each managed Service should have its own managed namespace.
* The operator should populate the Status field inside the installation CR, such that the user knows the progress of the (de)provisioning.
* The resources provisioned from the instantiation of the CR should be watched by the MSS Operator, e.g. deployment configs etc so if a user manually removes a deployment config associated to the service, the operator will return the service to the correct state e.g. create the deployment config again. - NOT MANDATORY (/)
* Operator should be capable of updating the MSS to a new version, when a new version of MSS is released.
* The MSS dependency on PostgreSQL needs to be handled. Use of the existing PostGreSQL operator is preferable. (!)
h4. [MSS Consumption CR] As a Developer, I want to be able to specify necessary info through a CR, such that I can associate my Mobile App with the MSS.
Trelo Link: https://trello.com/c/ExZqTlJ6/12-mss-consumption-cr-as-a-developer-i-want-to-be-able-to-specify-necessary-info-through-a-cr-such-that-i-can-associate-my-mobile
|
|
