Re: Changing Prometheus rules

Hi Tim, You need to stop cluster-monitoring-operator than and then edit configmap. If cluster-monitoring-operator is running while editing configmap it will always revert it to default. Uz pozdrav, Vladimir Remenar From: Tim Dudgeon To: Simon Pasquier Cc: users Date:

Re: sftp service on cluster - how to do it

I guess one could use either Service.type=LoadBalancer (one ELB per service on port 22) or Service.type=NodePort with single ELB mapping ELB-PORT:NODE-PORT for each service. -- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 Em

Re: Changing Prometheus rules

The KubeAPILatencyHigh alert fires several times a day for us (on 2 different OKD clusters). On 18/11/2019 15:17, Simon Pasquier wrote: The Prometheus instances deployed by the cluster monitoring operator are read-only and can't be customized.

Re: OKD 3.11 - Volume and Claim Pre-binding - volumes for a namespace

Ended up doing the same thing with a validating webhook using OPA On Mon, Nov 18, 2019, 4:13 AM Alan Christie < achris...@informaticsmatters.com> wrote: > Thanks, > > I was wondering whether I could create an arbitrary storage class so (if > the application can be adjusted to name that class)

Re: Changing Prometheus rules

The Prometheus instances deployed by the cluster monitoring operator are read-only and can't be customized. https://docs.openshift.com/container-platform/3.11/install_config/prometheus_cluster_monitoring.html#alerting-rules_prometheus-cluster-monitoring Can you provide more details about which

Changing Prometheus rules

What is the "right" way to edit Prometheus rules that are deployed by default on OKD 3.11? I have alerts that are annoyingly noisy, and want to silence them forever! I tried editing the definition of the PrometheusRule CRD and/or the prometheus-k8s-rulefiles-0 ConfigMap in the

Re: OKD 3.11 - Volume and Claim Pre-binding - volumes for a namespace

Thanks, I was wondering whether I could create an arbitrary storage class so (if the application can be adjusted to name that class) this might well be a solution. I’ll poke around today, thanks. Alan Christie achris...@informaticsmatters.com > On 18 Nov 2019, at 12:08 pm, Frederic Giloux

Re: OKD 3.11 - Volume and Claim Pre-binding - volumes for a namespace

Hi Alan you can use a storage class for the purpose [1] and pair it with quotas for the defined storage class [2] as proposed by Samuel. [1] https://docs.okd.io/3.11/install_config/storage_examples/storage_classes_legacy.html#install-config-storage-examples-storage-classes-legacy [2]

Re: OKD 3.11 - Volume and Claim Pre-binding - volumes for a namespace

Not that I know of. The claimRef is not meant to be changed manually. Once set, PV should have been bound already, you won't be able to only set a namespace. Have you considered using ResourceQuotas? To deny users in a Project from requesting persistent storage, you could use the following:

OKD 3.11 - Volume and Claim Pre-binding - volumes for a namespace

On the topic of volume claim pre-binding … Is there a pattern for creating volumes that can only be bound to a PVC from a known namespace, specifically when the PVC name may not be known in advance? In my specific case I don’t have control over the application's PVC name but I do know its

Re: external ips - seems like handwaving in docs

Hi, External IPs relies on either: - some cloud integration, which would provision some kind of LoadBalancer, then the allocated IP would show back as our Services external IP - with bare-metal: some pre-configured subnet, a pool of IPs that may be allocated to those services (I didn't see this