I am evaluating Google Config Connector to create resources in GCP alongside our applications. The connector creates labels on the resources it creates and these “Octopus.*” names are invalid for label keys in GCP. The connector won’t try to create GCP labels that have prefixes such as “my.prefix/key”.
I’m sorry to be the bearer of bad news once again but at the moment those values are hard-coded into our steps and are used by Octopus during the deployment.
The only way I can imagine to not have these would be to use a regular run a script step and code the creation of the resources yourself, which would ultimately defeat the purpose of using one of our kubernetes steps.
I’m sorry I haven’t been able to provide you with good news today, but please don’t hesitate to get back in touch in the future should you have any issues.