gruntwork-io/kubergrunt

kubergrunt eks configure should allow you to force update an existing context

Open

#116 opened on Mar 31, 2021

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (92 forks)auto 404
enhancementgood first issue

Repository metrics

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

Description

When you reuse EKS cluster names, the ARNs stay the same if the EKS cluster is recreated, but since the server parameters change (e.g., the endpoint and the CA certificate), you need to reconfigure the kubeconfig. However, kubergrunt currently errors out if a context and config already exists for the server with the same ARN.

The workaround is to delete the existing config, but kubergrunt eks configure should also expose a --force option to overwrite the existing config instead of erroring out.

Contributor guide

Research direction
Examine the current implementation of 'eks configure' in kubergrunt to understand how it checks for existing context and errors. Then add a force flag that overwrites the existing configuration when set, ensuring the update logic respects the flag and updates endpoint and CA certificate accordingly.
Tech stack
go
Domain
clidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60