Erick Fejta
Erick Fejta
This seems to be failing tests, would you like to try and fix the tests or close out this PR?
They are always created, https://github.com/bazelbuild/rules_k8s/blob/a84d15926a882129b724105039ef804b8cbc6eb5/k8s/object.bzl#L524
The code you're looking for is here: https://github.com/bazelbuild/rules_k8s/blob/0a04716c226d0173bf7035965d9010871d39142b/k8s/object.bzl#L496-L587 k8s_object is a macro (aka function) which calls stuff like: https://github.com/bazelbuild/rules_k8s/blob/0a04716c226d0173bf7035965d9010871d39142b/k8s/object.bzl#L527 https://github.com/bazelbuild/rules_k8s/blob/0a04716c226d0173bf7035965d9010871d39142b/k8s/object.bzl#L539 that actually declare these targets. This would probably involve putting...
This sounds interesting if someone wants to take it on, otherwise I'm going to close this out as it is the current intended behavior.
ref https://github.com/bazelbuild/rules_k8s/issues/568
/kind oncall-hotlist
Correct, @google-oss-robot needs write access to the repo in order to update status contexts. We are seeing the following error: ```yaml jsonPayload: { component: "tide" controller: "status-update" error: "status code...
Just took over oncall today from Ben, let me investigate more and report back