googlecloudplatform / csp-config-management Goto Github PK

This README has a link to https://cloud.google.com/anthos-config-management/docs/repo, which 404s. It's possibly supposed to be one of:

• https://cloud.google.com/anthos-config-management/docs/concepts/configs
• https://cloud.google.com/anthos-config-management/docs/concepts/hierarchical-repo

I think these two files are artifacts of Aggregated Resource Quota which is no longer in Anthos Config Managment and should be deleted. I don't see any corresponding resources in my cluster that represent these objects so I think they are ignored and will just confuse readers who seek to understand this example.

csp-config-management/foo-corp/namespaces/online/shipping-app-backend/quota.yaml
csp-config-management/foo-corp/system/resourcequota-hierarchy.yaml

Also renaming this repository to anthos-config-management will improve search-ability and brand compliance.
thanks

https://cloud.google.com/csp-config-management/docs/ is referred at multiple places and returns HTTP 404.

• https://github.com/GoogleCloudPlatform/csp-config-management/blob/master/README.md refers to https://cloud.google.com/csp-config-management/docs/
• https://github.com/GoogleCloudPlatform/csp-config-management/tree/master/foo-corp refers to https://cloud.google.com/csp-config-management/docs/quickstart

what is the recommended way of storing/configuring secrets for applications?

How would you deploy for example prometheus operator with config sync Manual guide
The problem is that the CRD is created by the operator and not resolvable by config sync during the initial sync when trying to deploy from a repository containing prometheus objects config sync will complain with the following error:

[1] KNV1021: No CustomResourceDefinition is defined for the type "Prometheus.monitoring.coreos.com" in the cluster.
Resource types that are not native Kubernetes objects must have a CustomResourceDefinition.

source: namespaces/monitoring/monitoring-namespaced-resources.yaml
namespace: monitoring
metadata.name: acm
group: monitoring.coreos.com
version: v1
kind: Prometheus

The same is also true when trying to deploy gatekeeper with gatekeeper policies in the same repo.