newrelic-kubernetes-operator
newrelic-kubernetes-operator copied to clipboard
newrelic
Operator to create New Relic configuration in Kubernetes
### Objective Add support for Muting rules ### Acceptance Criteria New CRD for Muting rules CRUD operations for managing Muting rules
### Objective Add support for NRQL Baseline alert conditions ### Acceptance Criteria New CRD for Synthetics NRQL Baseline alert conditions CRUD operations for managing NRQL Baseline alert conditions
### Objective Add support for Synthetics Multi-Location alert conditions ### Acceptance Criteria New CRD for Synthetics Multi-Location alert conditions CRUD operations for managing Synthetics Multi-Location alert conditions
### Description When attempting to apply an `AlertsPolicy` configuration that includes an alert condition that omits the condition's `type` field, running `kubectl apply` silently fails and makes it seem like...
### Feature Description There are several places where the operator needs API keys in order to work correctly. Many of those keys want to be protected as kubernetes Secrets. Examples...
### Current behavior Deleting lines [10-22](https://gist.github.com/sanderblue/5d9337e11e19be138a9c3fa38c2fb35d#file-k8s-new-relic-alert-policy-yaml-L10-L22) from code snippet below, then running `kubectl apply` does not delete the NRQL alert condition. ```yaml apiVersion: nr.k8s.newrelic.com/v1 kind: Policy metadata: name: my-policy spec:...
### Objective Certain properties of the Alert Policy definition should have default values in case the user doesn't need/want to set them. As an example, the following properties currently do...
### Description If you have an alert policy configured with an "invalid" alert condition, the policy will be created, but an invisible, sneaky, silent error will occur under the hood...
### Description Currently a user is required to supply the `region` field as part of the `spec` for the `Policy` configuration. This should be not required. If the user does...
### Feature Description We would like to programmatically add accounts to the AWS integration, for example. This pair of NerdGraph mutations might do the trick. ``` graphql mutation { cloudLinkAccount(accountId:...