The console-plugin repository currently contains hardcoded GroupVersionKinds (GVKs) for Kubernetes resources such as dnspolicy, ratelimitpolicy, authpolicy, and tlspolicy. These GVKs may differ from the versions used by the kuadrant-operator on the main branch.
To ensure the console-plugin remains in sync with the latest versions from the kuadrant-operator, we should implement an automated check. This check should compare the GVKs from the kuadrant-operator with those in console-plugin. If any discrepancies are found, a pull request should be automatically created to update the GVKs in console-plugin.
Requirements:
Identify the GVKs in use for dnspolicy, ratelimitpolicy, authpolicy, and tlspolicy in the kuadrant-operator.
Compare these with the hardcoded GVKs in the console-plugin.
If differences are detected, trigger an automatic PR to update the GVKs in the console-plugin.
Consider implementing this as a GitHub Action, possibly using a scheduled workflow to run this check regularly.
The
console-pluginrepository currently contains hardcoded GroupVersionKinds (GVKs) for Kubernetes resources such asdnspolicy,ratelimitpolicy,authpolicy, andtlspolicy. These GVKs may differ from the versions used by thekuadrant-operatoron themainbranch.To ensure the
console-pluginremains in sync with the latest versions from thekuadrant-operator, we should implement an automated check. This check should compare the GVKs from thekuadrant-operatorwith those inconsole-plugin. If any discrepancies are found, a pull request should be automatically created to update the GVKs inconsole-plugin.Requirements:
dnspolicy,ratelimitpolicy,authpolicy, andtlspolicyin thekuadrant-operator.console-plugin.console-plugin.