Block a user
feat(example): added an example of packaging a rust app from github
added a monitoring stack that works with openshift/okd. Okd needs to use the cluster observability operator in order to deploy namespaced prometheuses and alertmanagers
I scanned very briefly the CRDs, so I trust you on this ;)
added a monitoring stack that works with openshift/okd. Okd needs to use the cluster observability operator in order to deploy namespaced prometheuses and alertmanagers
considering we run the update below, I don't think we need to keep this
added a monitoring stack that works with openshift/okd. Okd needs to use the cluster observability operator in order to deploy namespaced prometheuses and alertmanagers
shouldn't it have a release name?
added a monitoring stack that works with openshift/okd. Okd needs to use the cluster observability operator in order to deploy namespaced prometheuses and alertmanagers
Do we really to keep different monitoring strategies? Instead of just providing one (opinionated) Monitoring feature?
fix/argo
It's probably a bit too much to fix it now, but indeed the Topology should provide the capability to get the host domain. Actually it should probably provide a higher level capability: create domain for a service (<-- example of a Tell Don't Ask).
feat: add remote_url! and local_folder! macros to make Url easier to create
fix/argo
Is there a way to not have to provide this? It seems to me that the end user shouldn't have to worry about it and that it should be handled by the topology.
