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

Akamai regions may be unavailable for physical clusters #2396

Open
1 task done
mrsimonemms opened this issue Jan 23, 2025 · 1 comment
Open
1 task done

Akamai regions may be unavailable for physical clusters #2396

mrsimonemms opened this issue Jan 23, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@mrsimonemms
Copy link
Contributor

Which version of kubefirst are you using?

main

Which cloud provider?

Akamai

Which DNS?

None specific

Which installation type?

None specific

Which distributed Git provider?

None specific

Did you use a fork of gitops-template?

No

Which Operating System?

None specific

What is the issue?

It's possible for Akamai regions to be unavailable. There should be a check in the API to only return available regions/node sizes.

Image

This is a bugfix. I would prefer for this to be wholly rewritten to actually communicate a provider outage better.

Code of Conduct

  • I agree to follow this project's Code of Conduct
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

No branches or pull requests

1 participant