You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is to improve the intelligence to our cluster counting mechanism so that we can identify when clusters that we’re tracking are no longer available, and not incorrectly include them in our billing calculations.
The issue is if you don't remove the clusters from the kubefirst pro app, saas is never updated that they have been removed, and we keep charging as if they've been up the whole time. obviously, this will make people a little sad when they get the bill.
This has been updated in the existing documentation but we want the UI/UX to be much better in handling this.
The text was updated successfully, but these errors were encountered:
This ticket is to improve the intelligence to our cluster counting mechanism so that we can identify when clusters that we’re tracking are no longer available, and not incorrectly include them in our billing calculations.
The issue is
if you don't remove the clusters from the kubefirst pro app, saas is never updated that they have been removed, and we keep charging as if they've been up the whole time. obviously, this will make people a little sad when they get the bill.
This has been updated in the existing documentation but we want the UI/UX to be much better in handling this.
The text was updated successfully, but these errors were encountered: