dataiku / dataiku/dss-plugin-eks-clusters
handle outdated version of eksctl
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4
- Forks
- 5
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 1
Description
Goal
Avoid the situation when an outdated version of eksctl prevents starting a newer (unsupported by ekstl) version of K8s e.g. eksctl 0.20.0 and EKS 1.20 (ticket #25221)
[2021-08-17 19:46:08,793] [25987/MainThread] [INFO] [root] 2021-08-17T19:46:08Z [ℹ] eksctl version 0.20.0
..
[2021-08-17 19:46:08,793] [25987/MainThread] [INFO] [root] Error: invalid version, supported values: 1.13, 1.14, 1.15, 1.16
Notes
current logic in def get_eksctl_or_fetch() present several issues:
- check for outdated version of eksctl in
DATA_DIR/tmp/local_eksctl/or system-wide withwhich eksctl - when plugin does download eksctl, looks like untar should be executed for
eksctl_$(uname -s)_amd64.tar.gznoteksctl.tar.gz
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in python-lib/dku_aws/eksctl_loader.py at get_eksctl_or_fetch(). Check how versions are detected in DATA_DIR/tmp/local_eksctl/ and via which eksctl, then inspect the download extraction path for eksctl_$(uname -s)_amd64.tar.gz. Done means outdated installations are handled and the downloaded archive is extracted correctly for the reported EKS scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, python
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100