KusionStack / karpor / 42796149978

67%

main: 66%

Build Type

Pull #867

github

Committed by NopeCharon

Commit Message

fix(cluster): validate the current context and mask exec env in cluster objects

Validation picked the first cluster and user of the kubeconfig, while
creating the cluster goes through clientcmd and follows current-context.
A multi-context kubeconfig could therefore validate against one cluster
and register another. Resolve the cluster and user of the current
context for both the validation checks and the client config, and report
a missing or dangling current-context instead of falling back to the
first entries.

The Get/List sanitizer masked the token and certificates of a cluster
but left spec.access.credential.execConfig.env values readable. Mask
them as well, since they usually hold credentials such as
AWS_SECRET_ACCESS_KEY.

Signed-off-by: NopeCharon <115794254+NopeCharon@users.noreply.github.com>

Pull Request Pull Request #867: fix(cluster): accept exec-based kubeconfigs such as AWS EKS when validating

Coverage Stats

106 of 136 new or added lines in 2 files covered. (77.94%)

2 existing lines in 2 files now uncovered.

4637 of 6967 relevant lines covered (66.56%)

0.73 hits per line