Updated Project Template examples

[mfojtik]

• Dropping serviceLinks concept
• Service and podTemplate are now sharing the same schema as Kubernetes

[mfojtik]

@smarterclayton @csrwng @VojtechVitek review pls.

[smarterclayton]

LGTM

[VojtechVitek]

lgtm

[VojtechVitek]

@mfojtik we're going to add the replica parameter examples in the subsequent PRs, right?

[smarterclayton]

Why is there a pod object here?

[smarterclayton]

Cancel LGTM, a few question

[mfojtik]

@smarterclayton JSON update, deployment can have multiple podTemplate defined (?) (if I understood that correctly ;-) Also added services.

@smarterclayton since now I'm confused ;-) I'm not sure if were talked about deploymentConfig having multiple deployments defined or a deployment have multiple podtemplates defined ;-)

[VojtechVitek]

@mfojtik imho multiple deploymentConfigs or deployments (which one?) having only one podTemplate

[mfojtik]

@smarterclayton

We discussed this on IRC with @csrwng that for the projectTemplate it makes sense to have multiple deploymentConfig defined for scenarios where you want to have frontend->database/caching/etc

However, once the project template is instantiated those deploymentConfigs will execute their deployments and that will result to 1+N deployments. We will need the somewhere store the information that these 1+N deployments belongs to a 'Project'. Does that makes sense?

[mfojtik]

@VojtechVitek good catch, yeah we will need to use plurals for arrays.

[mfojtik]

@smarterclayton ping?

is this good for merge and being picked up next sprint? or do we want to add more things as we discussed, like routing or API namespacing?

[mfojtik]

@VojtechVitek i'm thinking about nuking template_2 as this template is the same as template_1 example. No point of having both and updating both.

[VojtechVitek]

@mfojtik agreed, no need of multiple files atm.

[ncdc]

If we have more than 1 deploymentConfig, shouldn't this be called deploymentConfigs?

[VojtechVitek]

LGTM

[VojtechVitek]

The json file successfully validated with json schema from #25