- fix container name
- the volume-from label works only with "same-pod" label of course. It
allows the use of the same volume from another service to be shared in
a same pod. E.g. php-fpm + nginx
- ingress can now have annotations
- configmaps are better named and there is a label to know from where
the content is taken
- fixed bad "nil" pointer checks
- we force to not resolve paths from compose file, this should be a
problem when we call the compose file from outside. So, TODO: check
this!
- the "project" label is now the Chart Name, not a static string
- minor fixes
- image of container is now splitted in repository and tag (in values
and deployment). The "tag" is tested in deployment
- add "chart-version" option
Code:
- globalize the PVC generation
- ensure types for environment values
- refactored to make generic the container creation in a deployment
- avoiding race condition on ServiceConfig by using a copy (then a
pointer of this copy)
- variables are all in values.yaml as "template string". This means that
we can now set values to reference others (useful with mapenv label)
- we can also set any variable as a secret
- that means that katenary.io/env-to-service is now DEPRECATED
- the yaml style in label is OK, that allows more possibilities and
adaptation for users
- we didn't get probe configuration from compose, it's now fixed
- the HealthCheck object is tricky because it overrides `time.Duration`,
we are using specific initialization in NewProbeWithDuration
- it is easier to pass the ServiceConfig to NewProbeFromService
We can now manage "- A=B" format as "A: B"
Some others properties than environment may have this problem (e.g.,
command) so we will fix this later.
fix#4
