Summary:
I7a. Bootstrap disk space issue
This EC2 instance has two volumes
a) 8GB
b) 50GB encrypted not available to use.
The disk was packed on the second download of tanzucli tools (src/install-tools.sh). see error
8GB is not enough. Bump up 8GB to 16GB.
R7a. This is a new and I’m able to replicate as of yesterday. It’s been working fine up until recently, but the xvda device mapping specification is now mapping to a secondary device. Working on figuring this out.
I7b. Also, not sure about the use of 50 GB encrypted disk?
R7b. I must insist on encrypting the disk since we’re writing clear-text credentials to disk in the generated tap-values.yaml. I previously saw in the ytt docs that we can store the config in memory and there’s some options for secrets management, but haven’t had a chance to dive deep on this. If we don’t write clear-text credentials to disk, disk encryption doesn’t need to be a requirement. What’s the concern with encrypting the disk?
Summary: I7a. Bootstrap disk space issue This EC2 instance has two volumes a) 8GB b) 50GB encrypted not available to use. The disk was packed on the second download of tanzucli tools (src/install-tools.sh). see error 8GB is not enough. Bump up 8GB to 16GB. R7a. This is a new and I’m able to replicate as of yesterday. It’s been working fine up until recently, but the xvda device mapping specification is now mapping to a secondary device. Working on figuring this out. I7b. Also, not sure about the use of 50 GB encrypted disk? R7b. I must insist on encrypting the disk since we’re writing clear-text credentials to disk in the generated tap-values.yaml. I previously saw in the ytt docs that we can store the config in memory and there’s some options for secrets management, but haven’t had a chance to dive deep on this. If we don’t write clear-text credentials to disk, disk encryption doesn’t need to be a requirement. What’s the concern with encrypting the disk?
Suggested Assignee: Troy Priority: P0