Fix encryption-config.yaml is missing issue

[chiukapoor]

Updates

• Add configs/encryption-config.yaml file
• Update .gitignore to not ignore configs/encryption-config.yaml file

Issue

• Fixes: configs/encryption-config.yaml is missing #768

[mikerybka]

Right on!

[kbenson]

Just ran into this problem and had to look up an issue to find a solution. If this ensures the file is present, seems like it should be accepted. The directions as written have a breaking bug without this.

[chiukapoor]

@kelseyhightower please review the PR.

[tom-ludwig]

For me, this throws an error. But this works:

Suggested change

	apiVersion: v1
	apiVersion: apiserver.config.k8s.io/v1

[DEmmons]

This is a great help, but there's an issue with this approach - in the course of completing lab 06-data-encryption-keys.md a copy of this file is made in the root of the repo, with the encryption key in it. The .gitignore entry is needed to prevent this from being committed back to the repo when changes are made. a simple solution is to name the missing file 'configs/encryption-config-template.yaml' so .gitignore will not match it, and update the relevant line in 06-data-encryption-keys.md accordingly to reference it.

[edit: never mind, this is already addressed]

[chiukapoor]

This is a great help, but there's an issue with this approach - in the course of completing lab 06-data-encryption-keys.md a copy of this file is made in the root of the repo, with the encryption key in it. The .gitignore entry is needed to prevent this from being committed back to the repo when changes are made. a simple solution is to name the missing file 'configs/encryption-config-template.yaml' so .gitignore will not match it, and update the relevant line in 06-data-encryption-keys.md accordingly to reference it.

The .gitingore file still prevents encryption-config.yaml in the root of the repo from being accidentally committed. I just have added another condition to allow the encryption-config.yaml in the configs folder

[richabanker]

Also ran into this recently, thanks for the PR!

[benjaminapetersen]

Working on this today as well and noticed the missing file. 👍

[oates]

I came looking for a PR on this before doing the work myself. I also ran into the issue and had to do a workaround by manually creating the file. Having the file in the config folder would resolve the issue. Thanks for the PR @chiukapoor