att-comdev
guidelines: Helm standardization of values key:pairs (and nesting)
Once the initial 0.1.0 release is cut I think it would be good idea to formally define a structure for use within values.yaml, this will make the orchestration of multiple services much easier to manage and provide a source of truth for both new contributors and services to use as a reference source.
In particular, I think this should cover (as a starting point):
- Image Tags & Pull Policy
- Resouces:
- Replicas
- RAM/CPU allocation
- Service/Networking
- Ports
- K8s Service name/type
- Ingress
- Namespacing
- Keystone
- Admin Creds
- Service Creds
- Database
- URI
- Admin Creds
- User Creds
- Service specific config (a generic structure layout)
@mcnanci let's add this to a 0.2.0 release, when the schedule is ready. this is an important one, and we've been touching around it anyway.
@intlabs i think this is still being fleshed out a bit (i think we're almost there, but could be some room for a little improvement). i will start to look at some methods i think will be appropriate for us later tonight. i want to take a stab at this, and will present something very soon. assigning myself.
Awesome, would be good to get this together as a cohesive picture :) I think that the work @alanmeadows is doing as part of https://github.com/att-comdev/openstack-helm/pull/262 and the Keystone Endpoint work we just merged goes a huge way toward this goal. Off the top of my head only really Image Tags & Pull Policy along with Resouces (Replicas & RAM/CPU allocation) from the original set of bullet points are not in progress in one form or another.
I think we're at a good spot with targeting the points laid out in this issue. We can address the remaining points @intlabs laid out once we move into OpenStack. I'm happy with our progress on this front across the project. @intlabs @larryrensing thoughts?
