Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect kubernetes version parsing: "1.30" returned as "1.3" #1958

Closed
sykim-etri opened this issue Jan 20, 2025 · 1 comment · Fixed by #1959
Closed

Incorrect kubernetes version parsing: "1.30" returned as "1.3" #1958

sykim-etri opened this issue Jan 20, 2025 · 1 comment · Fixed by #1959
Labels
bug Something isn't working

Comments

@sykim-etri
Copy link
Member

What happened
: /availableK8sVersion (aws, ap-northeast-2) 호출시 버전 정보를 비정상적으로 리턴하는 경우가 있다.
예를 들어 assets/k8sclusterinfo.yaml에는 1.30으로 기재되어 있는데, 1.3으로 리턴한다.

  {
    "name": "1.3",
    "id": "1.3"
  },

What you expected to happen
: assets/k8sclusterinfo.yaml에 기재된 정보를 그대로 리턴

How to reproduce it (as minimally and precisely as possible)
: 항상 재현

Environment

  • Source version or branch: v0.10.4
@sykim-etri sykim-etri added the bug Something isn't working label Jan 20, 2025
@sykim-etri
Copy link
Member Author

Viper가 아래의 정보를 소수점으로 인식하여 변환하고 있는 것으로 파악되었습니다.

  available:
    - name: 1.30
      id: 1.30

Viper 설정 등으로 해결이 잘되지 않는 상황이며, 간단히 명시적으로 문자열임을 나타내도록 assets/k8sclusterinfo.yaml을 수정할 예정입니다.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant