kubernetes-sigs/cluster-api-provider-aws

Clear out sensitive files after successful bootstrap

Open

#2,208 opened on Jan 14, 2021

View on GitHub
 (19 comments) (0 reactions) (0 assignees)Go (689 forks)auto 404
area/securityhelp wantedkind/featurelifecycle/rottenneeds-triagepriority/important-longterm

Repository metrics

Stars
 (723 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind feature

We keep around some files around that contain sensitive information that should ideally be removed when all conditions are met for proper cluster creation. I would like to have a high level of confidence that everything from those files has properly been used, and then the file can be safely deleted without impacting future troubleshooting or remediation.

Describe the solution you'd like Delete sensitive files that are no longer used to reduce the protected locations on the given VM.

Anything else you would like to add: Some of this might require changes to Cluster API and not just Cluster API Provider AWS.

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.