I thought we had a default quota view

[drewr]

Created a project and DNS zone yesterday. I would expect my quota information to be populated.

Project: drewr-y4nd1b

@mattdjenkinson @scotwells

[scotwells]

@drewr what's your project name so I can debug?

[drewr]

Ah yes, Project: drewr-y4nd1b

[scotwells]

Thanks. Confirmed this is because the cloud portal is trying to retrieve quota resources from the wrong namespace.

[drewr]

This is coming in https://github.com/datum-cloud/cloud-portal/releases/tag/v0.2.34, thanks for the fix @scotwells!

[drewr]

....and it works:

[drewr]

This happened again with a new project drewr2-iz7s3o.

[drewr]

@mattdjenkinson If the namespace fix was in before why would it be per-project or depend on its status?

[mattdjenkinson]

@scotwells when listing quotas for a project that doesn't have any resources yet we just get an empty array. We use the namespace milo-system when querying for project level quotas, is that correct?

  apiVersion: "quota.miloapis.com/v1alpha1",
  items: [],
  kind: "AllowanceBucketList",
  metadata: {
    continue: "",
    resourceVersion: "707407282",
  }

[scotwells]

I think we have a separate issue related to quota resources not being consistently being re-created for projects. Noticed that when I was testing the changes in staging and the allocation buckets weren't created for my project but they were for others.

I'll take a look at this today and see if I can find the cause.

[scotwells]

Was able to track down the issue and opened a PR to resolve it.

[scotwells]

@drewr can you confirm this is working for you now? I released milo v0.16.2 with a fix and confirmed my project is showing the expected quota limits.

[drewr]

Looks like it is! Created a new project and showing zeroes. Although, shouldn't I see 0/N proxies as well?

[scotwells]

@drewr we don't have limits in place for proxies today

[drewr]

That explains it!