Open akranga opened 4 years ago
After the spot data subscription is made the feed content is not filled instantly.
So the next deployed kubecost
does not found the feed on the just made target bucket.
It is to check would kubecost
do the checks periodically in the future.
related #427
kubecost
accepts only plain user credentials to grand access to a sot data bucket.
Meanwhile the regular profile auth works well.
@akranga should we add some readiness waiter to be sure the user faced fronted is up after component is deployed?
I as a user want to deploy a kubecost component through the happy meal
terraform bucket
as default place. Or arbitrary bucket if neededprometheus
,grafana
behaviorKubecost token. flowkubecost
"late binding" on spot data feed