@reubenvanammers Thank you for your feedback. We will look into being able to specify the resource ID in the spec and will let you know when we have more information.

K8s limits character set to a-z0-9?

Here's an example:

bigquerydataset.bigquery.cnrm.cloud.google.com/x unchanged

The BigQueryDataset "x_y" is invalid: metadata.name: Invalid value: "x_y": a 
DNS-1123 subdomain must consist of lower case alphanumeric characters, 
'-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', 
regex used for validation is 
'[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

Is there any workaround?

Tangentially related: #112

@max-sixty thank you for the additional details. Unfortunately, "-" or "_" can't be used in the BigQuery table or dataset names in KCC right now. We are looking into supporting the feature to specify the resource ID in the spec, and with that feature, users can specify BigQuery resource names with "_" in it. Will keep you updated if we have more information.

@AlexBulankou From https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names :

Most resource types require a name that can be used as a DNS subdomain name as defined in RFC 1123. This means the name must:

• contain no more than 253 characters
• contain only lowercase alphanumeric characters, ‘-’ or ‘.’
• start with an alphanumeric character
• end with an alphanumeric character

Is there a timeline on this? I was told it would be worked on during Q3

Hi @RoryShively , we're currently working on supporting resource name overrides and should have the feature out around the end of October.

I am having the same issue with Storage bucket names and KMS keys (as a policy we use underscore everywhere if possible and only fall back to dash in Kubernetes) while trying to convert our configuration management to Cloud Configuration.

closing as a duplicate of #25 (doing some light cleanup). Please watch that issue.

As mentioned, we plan on providing a new field which isn't subject to k8s naming restrictions to specify the GCP resource name. The current ETA is by first week of January.