michelleN/Meeting Notes - Feb 5th, 2019

## Meeting Notes - Feb 5th, 2019
Ryan is someone at a company who is using Kubernetes and Azure. Have some legacy stuff but transitioning most services on to AKS.

Questions he asked:
- Should I check in draft artifacts (charts, Dockerfile, draft.toml)?
  Personally, I check in the Dockerfile, draft.toml, and the charts so that developers have access to it if they need it. We can in the future make the location of the charts within the git repository configurable so that if we want to hide it somewhere else we should be able to.
- Do I use draft in my CI/CD pipeline?
  -- No. You should only be re-building the docker image and pushing it the container registry and then using that image with a production chart for your app which lives in a chart repository for your org.
  -- You _can_ use it in your CI for testing though. That makes sense.
- What kind of patterns do I follow to be able to use generic charts? Chart for every type of app? Generic chart for all web apps? How do I use values files?


Other notes:
-- Packs make Draft special. Packs are used so that your org can standardize on what base images or annotations or things you all want to use (for security and other concerns) and then it lets you package that somewhere for re-use by your developers.
-- What should a developer know and what should a dev not care about when it comes to containers and k8s? Developers should understand at a high level the Dockerfile and be able to read it. They should understand that their app will go in a container and expose a port.
	Ryan is someone at a company who is using Kubernetes and Azure. Have some legacy stuff but transitioning most services on to AKS.

	Questions he asked:
	- Should I check in draft artifacts (charts, Dockerfile, draft.toml)?
	Personally, I check in the Dockerfile, draft.toml, and the charts so that developers have access to it if they need it. We can in the future make the location of the charts within the git repository configurable so that if we want to hide it somewhere else we should be able to.
	- Do I use draft in my CI/CD pipeline?
	-- No. You should only be re-building the docker image and pushing it the container registry and then using that image with a production chart for your app which lives in a chart repository for your org.
	-- You _can_ use it in your CI for testing though. That makes sense.
	- What kind of patterns do I follow to be able to use generic charts? Chart for every type of app? Generic chart for all web apps? How do I use values files?


	Other notes:
	-- Packs make Draft special. Packs are used so that your org can standardize on what base images or annotations or things you all want to use (for security and other concerns) and then it lets you package that somewhere for re-use by your developers.
	-- What should a developer know and what should a dev not care about when it comes to containers and k8s? Developers should understand at a high level the Dockerfile and be able to read it. They should understand that their app will go in a container and expose a port.