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.

Sign up for GitHub

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

Jump to bottom

Broken Alibaba Integration #2738

Open
moskitone opened this issue May 7, 2024 · 4 comments
Open

Broken Alibaba Integration #2738

moskitone opened this issue May 7, 2024 · 4 comments
Labels
E3 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project needs-follow-up needs-triage opencost OpenCost issues vs. external/downstream P2 Estimated Priority (P0 is highest, P4 is lowest)

Comments

@moskitone
Copy link

Describe the bug
There is an issue with the Alibaba integration in the new version.

2024-05-02T21:24:52.068794697Z ERR Controller: pullWatchers: failed to get config type for config with key: .../cn-beijing
2024-05-02T21:25:02.070025494Z ERR Controller: pullWatchers: failed to get config type for config with key: .../cn-beijing
2024-05-02T21:25:12.071081361Z ERR Controller: pullWatchers: failed to get config type for config with key: .../cn-beijing

https://github.com/opencost/opencost/blob/develop/pkg/cloud/config/controller.go#L114-L118
There are no types for the Alibaba cloud integration in https://github.com/opencost/opencost/blob/develop/pkg/cloud/config/statuses.go#L21-L33

Which version of OpenCost are you using?
Kubecost 2.2.2
@AjayTripathy
Copy link
Contributor

@moskitone could you describe impact? is the app in some sort of crash state or are you just unable to pull configs here?

@mattray mattray added P2 Estimated Priority (P0 is highest, P4 is lowest) E3 Estimated level of Effort (1 is easiest, 4 is hardest) opencost OpenCost issues vs. external/downstream kubecost Relevant to Kubecost's downstream project labels May 10, 2024
@moskitone
Copy link
Author

@AjayTripathy The Kubecost does not collect data from the cloud. Integration is not shown in the UI.

@AjayTripathy
Copy link
Contributor

Hi @moskitone are you referring to out of cluster costs? Those are not yet supported for Alibaba. It is on the roadmap however.

@moskitone
Copy link
Author

Hi @AjayTripathy.
Yes, I refer to the cloud costs.
Thanks. I will wait for the integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E3 Estimated level of Effort (1 is easiest, 4 is hardest) kubecost Relevant to Kubecost's downstream project needs-follow-up needs-triage opencost OpenCost issues vs. external/downstream P2 Estimated Priority (P0 is highest, P4 is lowest)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mattray @AjayTripathy @moskitone