Repository navigation
[Bug]: Default install requires GKE PodMonitoring CRD #2589
Description
What happened?
The default non-Kind install renders the base kustomization, which includes a Google Managed Prometheus PodMonitoring.
On standard Kubernetes clusters without that CRD, ate-setup deploy ate-system fails with:
no matches for kind "PodMonitoring" in version "monitoring.googleapis.com/v1"
Expected Behavior
The default installation should not require provider-specific CRDs. Move the PodMonitoring out of base, or skip this optional resource when its CRD is unavailable.
Steps to Reproduce
The default installation should not require provider-specific CRDs. Move the PodMonitoring out of base, or skip this optional resource when its CRD is unavailable.
Sandbox Runtime
gVisor (runsc)
Agent Substrate Version / Commit SHA
Kubernetes Version & Environment
No response
Host OS & Architecture
No response
Relevant Logs and Diagnostic Output
Additional Context
PR #1920 works around this through custom overlays but does not fix the default. A comment on #1782 reports the same problem on AKS, and PR #2241 removes the resource from its proposed AWS overlay.
Confirmation
- I have searched existing issues and verified that this is not a duplicate.
- I have verified that this issue occurs on the latest commit on
main.
Activity